Map Reasons to SIS
Overview
The “Map Reasons to SIS” section on the Reasons settings page lets you connect Orah custom reasons to the corresponding SIS reason codes / excuse types. This helps ensure Late/Absent attendance records sync to your SIS with the correct SIS reason.
Location
Admin Console → Supervise → Attendance → Insights Settings → Reasons
Understanding the Display
This section typically shows two groups:
Orah Custom Reasons (Editable)
These are reasons created in Orah by your team.
You can map each custom reason to an SIS reason code / excuse type
Unmapped custom reasons typically show
--and a warning indicatorThese should be mapped before relying on SIS sync/export for accurate reason codes
Reasons Created From SIS (Read-only)
These are reasons imported from your SIS via the SIS integration.
They are automatically linked to their corresponding SIS reason code
Their mapping is locked (cannot be changed in Orah)
How to Map Reasons
Go to Admin Console → Supervise → Attendance → Insights Settings → Reasons
Scroll to the “Map Reasons to SIS” section (usually near the bottom of the page)
Review the custom reasons list and identify any unmapped items (often shown as
--)Click “Open Reason Mapping”
In the modal, choose an SIS reason code / excuse type for each unmapped custom reason
Click “Save” to apply changes
Note: Only “Orah Custom Reasons” can be edited. Reasons imported from the SIS are locked.
Alert Messages (What They Mean)
If you see a red alert at the top of the page, common causes include:
“Please map all reasons …”
One or more Orah custom reasons are not mapped yet. Open the mapping modal and map every unmapped custom reason.
“Please sync reasons from SIS …”
Orah is not currently receiving SIS reasons. This usually means the Reason / Reason Code sync object is not enabled, a sync hasn’t been run yet, or the SIS isn’t providing reason codes.
Troubleshooting
“Map Reasons to SIS” section not visible
Your school may not have an active SIS integration, or the integration may not include SIS reason codes.
SIS reasons / excuse types not loading in the mapping modal
Refresh the page and try again
Confirm the SIS integration has Reason / Reason Code syncing enabled and a sync has successfully completed
Can’t edit SIS-created reasons
This is expected behavior. SIS-imported reasons are read-only in Orah; if you need additional options, create an Orah custom reason and map it to the appropriate SIS reason.
Do we need SIS “Present” reason codes?
Typically, Present records don’t require reasons. If an SIS “Present” reason code appears and causes confusion, it’s usually safe to remove it from Orah (depending on your SIS setup and school policy).