Skip to main content

Global Admin FAQ

Learn more about the Global admin role within Envoy, and how to manage your admin team.


About the Global admin role

Global admins have the highest level of access in Envoy. They can change settings, security controls, and admin permissions at every location in your company. Since one Global admin can affect every site, treat this role like any other privileged account in your organization. Give it to the people who need full control, and use location-based or custom admin roles for everyone else.

What are my permissions as a Global Admin?

You have full access to the following at all locations:

  • Security and compliance controls: the company-wide Block list, watch list, security match approvals, global sign-in flows, Approval workflows, and Visitor assessments

  • Admin management: assigning, editing, and removing admin roles at every location, assigning company-level roles (Global, Billing, Analytics Viewer), and creating custom admin roles

  • Employee records: your employee directory and its sync settings for all locations

  • Integrations: installing and editing company-wide and location-based integrations

  • Response: Emergency notification settings, templates, and messages

  • Visitors: visitor entries, invites, the visitor log, and Virtual Front Desk settings and call logs

  • Workplace: desks, maps and neighborhoods, employee reservations, rooms and calendar syncing, deliveries and delivery areas

  • Devices: Visitors, Rooms, and Delivery kiosks, and printers

  • Analytics: Occupancy, Attendance, Visitors, Workplace analytics, and custom dashboards

  • Locations: managing locations, location settings (name, address, logo, colors), and location groups

  • Billing: payment methods and plan subscriptions

  • Global overview: a single view of all locations and all admins

How many Global admins should we have?

Best practice is to have at least two, so someone still has full access if your primary Global admin is out, on leave, or leaves the company. One of them can be a service account your IT team controls.

Beyond that, every extra Global admin is one more person who can change security settings that protect every location. For example, a Global admin can:

  • Add or remove entries on the company-wide Block list, which screens visitors at every site

  • Edit global sign-in flows and approval policies that decide who gets into your buildings

  • Give other people admin access, including Global admin access

  • Change or disconnect integrations that sync your employee directory

Someone in HR who manages employee records doesn't need the ability to remove a person from your Block list. A facilities lead at one office doesn't need to change sign-in requirements at every other office. Giving them Global admin for convenience widens what any one account can change, and it makes an accidental or unauthorized change harder to trace.

💡Tip: You can see configuration changes in the Event log 💡

What should we use instead of Global admin?

Give each admin the narrowest role that covers their job:

If someone needs to...

Assign

Manage everything at one or a few sites

Location admin at those locations

Handle day-to-day visitor check-in

Manage plans and payment

View and share analytics

Manage employee records only (e.g., HR)

Custom company role with View and manage employees

Manage the company-wide Block list (e.g., Security)

Custom company role with Edit blocklist

Manage desk reservations without changing maps (e.g., EAs)

Custom role with Manage desk reservations (Assistants can also create reservations, if enabled)

Who can edit the Block list?

Global admins can add, edit, and remove Block list entries that apply to all locations. Location admins can only manage entries for the locations they're assigned to.

If a security team member needs company-wide Block list access without the rest of Global admin, create a company-level custom role with only the Edit block list permission and assign it to them. Learn more.

Tips and best practices

  • Review your Global admins regularly. In the Global overview, go to Manage > Admins and filter by role to see everyone with Global access. Remove access from anyone who no longer needs it.

  • Remove access as part of offboarding. If you use SCIM (Okta, Entra, OneLogin), you can provision and remove admin roles through group membership, so access ends when someone leaves the group.

  • Check the Event log. Global admins can review admin activity to see who changed what, and when.

Did this answer your question?