School Community

  • Personal Information
    Name/surname, date of birth, birth country, nationality, native language, government information, associations, etc.
  • Contact Details
    Address, phone, email and contact preferences
  • Relationships
    Family members, relatives and relevant others
  • Medical conditions, immunisations, sick bay visits, etc.

  • Arrival/departures, absences, day and class attendance

  • Classes (Students Only)
    Student data and timetable classes
  • Other School Details (Students Only)
    Previous and future schools, dates of change, year level details, etc.
  • Academic, athletic and all other student achievements

  • Detailed information of extra curricular activities and any relevant asset hire

  • Merit and demerit behaviour record

  • General and calendar events permissions

  • Diploma, certificates, credentials, licences, passports, etc.

  • Onsite/offsite events, diaries and timetabled classes

  • Billing family and responsibilities, discounts, payment configurations, and transaction and invoice information

  • Important Information and files

  • User Details
    Login type, username, password reset and roles
  • Staff Management (Staff Only)
    Government positions, status, full-time equivalent, start-end dates, category, etc.

A key part of the Educonnex design is an uncluttered, single-page application, that can hold the level of depth of information that schools can accumulate over time. The profile of each community member is the greatest testament of how well Educonnex does this.

Each community member profile has 11 different areas of information. Staff members have one additional area making a total of 12, and students have a total of 18. The different areas of the profile show the information in an interface that works best for what is being displayed, using intuitive designs to match processes that are being recorded.

In addition to controlling which community member profiles are visible to each user, different areas for each button, segments of these areas, and even whether the user can see, update, or deactivate, are all managed by Educonnex in the background. Each user only sees what they have access to. An example of this would be that a carer might be able to see their child’s sickbay visits, but be able to see and edit what medication can be administered to them. This is just another example of how schools can make Educonnex their own, by choosing how much each community member should engage with their own information, based on their role at the school.

The large majority of the Educonnex reports are built around around community member information.
If the existing reports don’t contain the information you require, Educonnex allows you to create your own extract, choosing the information and conditions that match your requirements.