Implementation Guide for Schools choosing to integrate with their Sentral Learning Management System or Student Management System

1. Overview

RollCall integrates with Sentral via secure API connection.

The integration automatically synchronises:

• Student records

• Parent/contact records

• Student–parent relationships

The integration runs nightly to keep RollCall aligned with your Sentral data.

Sentral is the source of truth. Changes made only in RollCall will not persist unless they also exist in Sentral.

2. What Data Syncs

Students

All students returned by Sentral as active are synchronised. Students cannot be selectively excluded.

The following student information is synchronised:

• Active / Inactive status

• Student Identifier (configured during setup — either “ID” or “Student Code” in Sentral)

• First Name

• Last Name

• Date of Birth

• Year Level

• Campus (must match a RollCall campus value)

Important: Student Identifier Selection

Sentral provides more than one student identifier (commonly “ID” and “Student Code”).

During setup, RollCall must be configured to use the correct identifier for your school.

If the incorrect identifier is selected:

• Students may fail to match correctly

• The preview may show large numbers of students being deactivated

If you are unsure which identifier your school uses, RollCall will confirm this with you during setup.

Parents / Contacts

Parent/contact records are:

• Created using the primary email address stored in Sentral

• Added as Unengaged

• Marked as Engaged once activated

• Marked as Past Parent if no longer eligible

The integration synchronises:

• First and Last Name

• Email address

• Mobile number (where available)

Duplicate email addresses are not permitted.

If a parent/contact no longer meets the eligibility rules, the student relationship is removed, and the record will be marked as Past Parent at the next nightly sync.

3. How Parent Eligibility Is Determined

Parent/contact eligibility in Sentral is based on how your school has configured:

• Contact priorities (e.g. Priority 1, Priority 2, etc.)

• “Lives With” status (where used)

RollCall can be configured to:

• Include specific priority levels only

• Include only contacts who live with the student (recommended in many cases)

Because each Sentral school is configured differently, RollCall will:

• Run a preview

• Review contact volumes

• Adjust eligibility settings if required before activation

If you wish to change what is being synchronised, refer to the Sentral – Frequently Asked Questions (FAQ) or contact RollCall Support.

4. Important Rules

When the API is active:

• Primary parents/contacts must originate from Sentral

• Any primary parent/contact added directly in RollCall will be marked as Past Parent at the next overnight sync

• Duplicate email addresses are not permitted

• Sentral remains the source of truth

Secondary carers may be added via the RollCall Parent App.

5. What to Expect When Going Live

There is no downtime for RollCall users. The integration does not interrupt daily operations.

During the first live sync:

• Parent/contact relationships may update to reflect Sentral rules

• Some contacts may be marked as Past Parent if they do not meet eligibility requirements

• Student statuses may update based on enrolment data

• Campus allocation will reflect the tenant/campus mapping provided

To minimise unexpected changes, we recommend reviewing in Sentral:

• Parent email addresses

• Contact priority levels

• “Lives With” settings (if used)

• Student enrolment dates

• Campus allocation / tenant setup (if multi-campus)

If you prefer activation during a term break, this can be scheduled.

6. Setup Instructions

For setup instructions, refer to: Sentral Integration – Setup & Activation Guide

7. Troubleshooting

If changes do not appear after the overnight sync, check:

• The correct student identifier has been selected (ID vs Student Code)

• A valid email address exists for the contact

• Contact priority configuration in Sentral

• “Lives With” status (if required)

• Campus/tenant mapping (if applicable)

• Duplicate email conflicts

For further assistance, refer to the Sentral – Frequently Asked Questions (FAQ).