Skip to main content
Set up GoGuardian Visitor sites and role assignments in GoGuardian Org Management before anyone signs in to Visitor. You need Super User access to Org Management, or a custom role with edit access to Visitor settings. Your organization signs up for Visitor as a district, but Visitor runs at the school level. A site tells Visitor which school or building uses it, who manages Visitor there, and which staff and students belong to that school.

Confirm Visitor Is Enabled

  1. Go to manage.goguardian.com and sign in with your Super User account.
  2. Open Product Settings and confirm Hall Pass/Visitor appears. If your organization has only Visitor, the menu is named Visitor. Use that name wherever this article says Hall Pass/Visitor.
  3. If neither appears, contact GoGuardian Support to confirm your organization’s license.
  4. Verify the result: You can open Sites without an access error.

Create a Site for Each School or Building

Each school or building that uses Visitor needs a site in Org Management. Sites are shared between GoGuardian Hall Pass and GoGuardian Visitor. If a school already has a Hall Pass site, see Turn On Visitor for an Existing Site instead.
  1. In Org Management, go to Product Settings → Hall Pass/Visitor → Sites.
  2. Click Add Site.
  3. Enter a name that helps users identify the school or building.
  4. If you see Enable Visitor for this Site, turn it on. This toggle appears only when your organization also has Hall Pass. Otherwise, Visitor is on for every site.
  5. If the school won’t use Hall Pass, turn off Enable Hall Pass for this Site. GoGuardian Org Management Edit Site page with Enable Visitor for this Site turned on and Enable Hall Pass for this Site turned off
  6. Click Save Site.
  7. Repeat these steps for each additional school or building.
  8. Verify the result: Each school or building appears in the Sites list.

Turn On Visitor for an Existing Site

Visitor isn’t turned on automatically for existing Hall Pass sites, so you choose which schools use it.
  1. Go to Product Settings → Hall Pass/Visitor → Sites.
  2. Click Edit for the site.
  3. Turn on Enable Visitor for this Site. Leave Enable Hall Pass for this Site as it is. GoGuardian Org Management Edit Site page with Enable Hall Pass for this Site and Enable Visitor for this Site both turned on
  4. Click Save Site.
  5. Verify the result: The site’s existing Admins, Staff, and Students now apply to both products.
Review the Admins tab before continuing. Every Site Admin now has full access to Visitor at this site. Front office staff who don’t use Hall Pass may not be on the Staff tab yet.

Assign Site Admins

The Admins tab assigns the Site Admin role. Site Admins set up Visitor for the site, change its settings, and have full access to every check-in point at the site.
  1. Go to Product Settings → Hall Pass/Visitor → Sites.
  2. Click Edit for the site.
  3. Select the Admins tab.
  4. Assign an organizational unit (OU) or individual user by following Add Organizational Units or Add Individual Users.
  5. Optional: To let Site Admins add users and change their site access from inside Visitor, turn on Allow Site Admins to manage user access.
  6. Click Save Site.
  7. Verify the result: The assigned user can open Visitor at the site with the Site Admin role.

Assign Staff and Students

Use the Staff tab for the staff who work at the site. Visitors can choose them as a host when checking in, and they receive a notification when their visitor arrives. Staff assigned to a room also receive a notification when a visitor or student chooses that room as their destination. Most staff never sign in to Visitor. The Staff tab alone doesn’t give anyone access to it. To let front office staff work the Front Desk, give them access inside Visitor after setup, as described in Users and Permissions. Use the Students tab for the students who can check in late, check themselves out, or be picked up by a parent or guardian at this site. Students don’t sign in to Visitor.
  1. Go to Product Settings → Hall Pass/Visitor → Sites.
  2. Click Edit for the site.
  3. Select Staff or Students.
  4. Assign an OU or individual user by following the applicable method below.
  5. Click Save Site.
  6. Verify the result: The assigned staff or students appear under Assigned OUs or Assigned Users on the tab. Visitors can now choose assigned staff as a host.

Add Organizational Units

Use an OU assignment when everyone in an applicable directory path needs the same role at a site.
  1. Open the site with Edit, then select Admins, Staff, or Students.
  2. In Available OUs, find the applicable OU path and select its checkbox.
  3. Click Add OU. The OU moves to Assigned OUs.
  4. Click Save Site.
  5. Verify the result: The OU appears under Assigned OUs, and its users have the selected role at the site.
An OU assignment includes only the users directly in that OU. For example, assigning /east_high/students doesn’t include students in /east_high/students/grade_9. To include them, assign /east_high/students/grade_9 too.

Add Individual Users

Use an individual assignment for an exception, such as a staff member who works at multiple sites or an administrator who needs a different role from their OU assignment.
  1. Open the site with Edit, then select Admins, Staff, or Students.
  2. In Available Users, find the user and select their checkbox.
  3. Click Add User. The user moves to Assigned Users.
  4. Click Save Site.
  5. Verify the result: The user appears under Assigned Users with the selected role at the site.
An individual user assignment overrides an OU assignment for that user. Assign staff who work at multiple sites at every applicable site.

Upload Individual Users with CSV

Use a CSV to assign multiple individual users to the selected role.
  1. Open the site with Edit, then select Admins, Staff, or Students.
  2. Click Upload CSV above Available Users.
  3. Add the CSV file.
  4. Click Add Users.
  5. Click Save Site.
  6. Verify the result: The uploaded users appear under Assigned Users for the selected role.
The CSV must contain 1 email address per row in a single column with no header. Each upload is limited to 500 users.

Set Up Guardians for Student Pickup

If the site uses the Parent/Guardian Pickup form, guardian records in Org Management let Visitor show each guardian the students associated with them. Visitor finds a guardian by the first and last name they enter at check-in, so guardian names in Org Management need to match. A guardian who checks in sees only their own students to pick up, unless the form’s Select Students step turns on Allow Non-Guardian Student Selection. Without that option, a guardian with no associated students sees No Students Found and a prompt to ask the front desk for help. Guardians aren’t assigned to a site. Manage them for your whole organization in one of these ways:

Verify Role and Site Access

Test Site Admin access before continuing with setup in Visitor. Staff and students don’t need to sign in, so review their assignments on the Staff and Students tabs instead.
  1. Sign in with a Site Admin test account.
  2. Confirm that Visitor appears in the GoGuardian product switcher.
  3. Open Visitor and confirm that the Front Desk shows the Set Up Visitor checklist for the correct site.
  4. Verify the result: The Site Admin reaches the expected site with full access.
Visitor appears in the product switcher at a site with Visitor turned on, for Site Admins and for staff assigned to a check-in point in Visitor. If a Site Admin doesn’t see it, confirm Enable Visitor for this Site is on. If a user can’t access a site, return to Product Settings → Hall Pass/Visitor → Sites, click Edit, and review the Admins, Staff, and Students tabs. Check the user’s individual assignment first because it overrides their OU assignment. If the user doesn’t exist in Org Management at all, see Troubleshoot Rostering and Sync Issues Across GoGuardian. If a staff member can’t open the Front Desk, give them access inside Visitor instead. See Users and Permissions. Next, finish setup in Visitor. See Set Up GoGuardian Visitor.

Resources

Last modified on November 3, 2026