Skip to main content

Checklist for Orah Attendance Insights Only

Use this guide if your school is using Orah for Attendance Insights, alerts, and absence reconciliation, but not taking class attendance in Orah.

Updated this week

πŸ”Ή TL;DR – Attendance Insights Only

Use this setup if your school wants to analyze attendance data, manage absences, create alerts, and use dashboards, but will not take class attendance in Orah.

You will:

  • Integrate your SIS and check all sync objects

  • Enable the Attendance History Object

  • Configure attendance reasons, passes, alerts, and dashboards

  • Use passes for absence reconciliation and future absences

You will NOT:

  • Take daily class attendance in Orah

  • Configure class roll types or attendance automation

πŸ‘‰ Best for schools using Orah as an attendance intelligence and reporting layer.

1. Account & Admin Access

  • Create your Orah account

    • Recommended: IT Admin / System Owner

  • Confirm Admin access for:

    • SIS integration

    • Single Sign-On (SSO)

    • Roles & permissions

    • Attendance configuration

Common issues to check

  • Account created by a non-admin user

  • Admin access removed after first login

  • Multiple admins are making conflicting changes


2. SIS Integration, SSO & Directory Sync

  • Set up SIS integration with Orah

  • In the SIS configuration, check all sync objects:

    • Students

    • Staff

    • Contacts / Guardians

    • Relationships

    • Enrollments

    • Year Levels / Grades

    • Classes / Groups

    • Schedules (if applicable)

  • Configure Single Sign-On (SSO)

  • Test staff login via SSO

  • Open the App Directory

  • Check all Sync Objects

  • Review contacts and relationships

  • Mark required contacts as Approved

  • Verify all the Sync objects and update auto sync

Common issues to check

  • Students missing β†’ enrollment or status not syncing

  • Contacts missing β†’ relationship object not enabled

  • Directory empty β†’ sync not completed or wrong scope

  • SSO works, but users see nothing β†’ role not assigned on login


3. Attendance History Object

  • Enable the Attendance History Object

  • Confirm it is enabled as a Sync Object under:

    • Admin β†’ App Directory β†’ SIS Integration

  • Select a Sync Start Date

    • Start of term or academic year

Common issues to check

  • No historical data β†’ history object not enabled

  • Partial data β†’ incorrect sync start date

  • Data gaps β†’ missing enrollments or schedules


4. Tags & School Branding

  • Create Tags (e.g. Year Level, Boarding/Day)

  • Apply tags to Students

  • Update School Pride:

    • School name

    • Logo

    • Terminology

Common issues to check

  • Tags created but not applied to students

  • Dashboard filters are incorrect due to tag logic

  • Tags applied to the wrong object type


5. Staff Roles, Permissions & Visibility

Configure the following roles:

Attendance Managers

  • All permissions except Admin

IT / Main User

  • Full Admin access

Teachers

  • Non-Admin

  • Assigned Students: SIS-assigned groups only

  • Emergency rolls: all students

  • Broadcast & communication: SIS students only

Expected behavior

  • Teachers should only see students based on their SIS assignments

Common issues to check

  • Teachers see no students β†’ Assigned Students not set

  • Teachers see all students β†’ Assigned Students misconfigured

  • Teachers see incorrect students β†’ SIS group sync issue

Configure Users

  • Configure users with the correct role and change the login method to SSO


6. Attendance Reasons & Permissions

  • Configure Attendance Reasons

  • For each reason, define:

    • Excused

    • Unexcused

    • Not Expected

  • Set visibility and permissions per role

  • Review SIS-provided reasons before creating new ones

    • Only add custom reasons if SIS reasons are not detailed or helpful

Common issues to check

  • Reasons not visible to correct users

  • Too many reason codes are causing reporting confusion

  • Excused status not defined correctly

  • Duplicate custom reasons were created unnecessarily


7. Passes & Parent Workflow

  • Configure Passes for:

    • Parents

    • Attendance team

  • Map Passes β†’ Attendance Reasons

  • Configure pass rules:

    • Approval rules

    • Timing rules

  • Copy and share the Secure Parent Pass Link

Common issues to check

  • Parent link not shared

  • Pass submitted but not reflected in insights

  • Pass workflow or rules not configured

  • Pass reasons not mapped to insights reasons


8. Alerts & Insights Dashboards

  • Create alerts for:

    • Attendance Managers

    • Contacts (if applicable)

  • Build dashboards:

    • Year-level

    • School-wide

  • Share dashboards with relevant staff

Common issues to check

  • Alerts created but not assigned

  • Dashboards not shared

  • Alert thresholds misconfigured


9. Training & Final Review

  • Watch Attendance Insights training videos

  • Review:

    • Widgets and dashboard sections

    • Alerts & Concerns

    • Absence reconciliation using passes

  • Complete a final system check:

    • Integration & sync objects

    • Roles & permissions

    • Attendance history

    • Reasons, passes, alerts, dashboards

If you’ve completed all the steps above and your dashboards, alerts, and passes are working as expected, you’re ready to start using Orah Attendance Insights.
If anything doesn’t look right, double-check the SIS sync objects, attendance history setup, and staff permissions, or reach out to Orah Support directly from the app β€” we’re happy to help.

Did this answer your question?