- OU mappings apply a role and site to everyone in a directory path (Organizational Unit). This is the primary method for most users.
- User mappings apply a role and site to a specific person, regardless of their OU. User mappings override OU mappings for that individual and are intended for exceptions.
Add Users via OU Mapping
Use OU mappings to give an entire student population or staff group access to a site.- Go to manage.goguardian.com and sign in with your district administrator account.
- Open the Hall Pass settings and go to the Mappings section for the site you are configuring.
- Click Add OU Mapping.
-
Enter the exact OU path for the group you are mapping. For example:
/school_a/studentsor/district/staff/east_high. - Select the site (school building) this OU should belong to.
- Select the role: Student, Staff, or Site Admin.
- Click Save.
- Verify the result: users in that OU can sign in to Hall Pass and see the correct site and role without a “no sites” error.
Add Individual Users via User Mapping
Use user mappings for exceptions: a staff member who supports multiple sites, an administrator whose OU would assign the wrong role, or a temporary staff member who needs access for a specific building.- Go to manage.goguardian.com and sign in with your district administrator account.
- Open the Hall Pass settings and go to the Mappings section for the site you are configuring.
- Click Add User Mapping.
- Enter the user’s email address.
- Select the site.
- Select the role: Student, Staff, or Site Admin.
- Click Save.
- Verify the result: the user can sign in to Hall Pass with the assigned role at the assigned site, regardless of their OU placement.
Troubleshoot Common Access Issues
”No Sites” Error on Sign-In
This error means Hall Pass found no OU mapping or user mapping that matches the user. To resolve it:- Confirm the user’s OU path in your directory (Google Admin Console or Active Directory).
- Check whether an OU mapping exists for that path in Org Management.
- If no mapping exists, create one. If a mapping exists, confirm the OU path in the mapping matches the user’s actual OU path exactly.
- If the match looks correct and the error persists, create an individual user mapping as an override.
Exact OU Path Matching
OU mappings use exact path matching. If your mapping is/school_a/students but a student’s OU path is /school_a/students/grade_9, the mapping may not apply. Use the OU path level your district standardizes on, and confirm that every user in scope falls within that path.
Unexpected Role Assignments
If a user’s role in Hall Pass does not match what their OU mapping would assign, check whether a user mapping exists for that person. Individual user mappings take precedence over OU mappings. A stale user mapping from a previous school year or role change can override the current OU mapping unexpectedly. To resolve it, find and update or remove the individual user mapping in Org Management.Multi-Site Staff
Staff who support more than one school need a separate mapping for each site. Without an explicit mapping for each site, the user sees only one building (or none at all) when they sign in. Use individual user mappings to grant access to each additional site.A User Is Missing from Hall Pass Entirely
If a teacher or student doesn’t appear in Hall Pass at all — not just the wrong role or site — there are two possible causes:- They aren’t mapped. Hall Pass shows only users covered by an OU mapping or user mapping. Confirm a mapping covers their OU (or add a user mapping), as described under No Sites Error on Sign-In.
- They aren’t in Org Management yet. Because Hall Pass has no roster of its own, a user who was never provisioned into Org Management can’t be mapped. Confirm the account exists in Org Management first. If it’s missing, resolve the underlying directory sync — see Troubleshoot Rostering and Sync Issues Across GoGuardian — or add the account manually in Manage User Accounts. Once the account exists, your mappings apply on the user’s next sign-in.
Remove or Deactivate a User
- Remove Hall Pass access only: Delete or change the OU mapping or user mapping that grants the user access. The change takes effect on their next sign-in.
- Deactivate the account entirely: Archive the user in Org Management. An archived account can no longer sign in to any GoGuardian product until it’s reactivated.