> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/smb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/smb/smb-app/team/user-privileges.md).

# User Privileges

There are three user roles within the system, each with different levels of privileges. These are Site Manager, Site Admin, and Site Member.

### Site Manager <a href="#site-manager" id="site-manager"></a>

Site Managers have full access to the system. They can:

* Receive alarm activation notifications and the optional Late to Arm reminder notification.
* Manage an alarm incident, including claiming and silencing the alarm, requesting a guard, and closing an incident.
* Add, edit, and remove users, and manage which areas Site Admins and Site Members have privileges for.
* Lock and unlock doors remotely.
* See the History Log.
* Set the Late to Arm notification time.
* Do everything Site Admins and Site Members can do.

### Site Admin <a href="#site-admin" id="site-admin"></a>

A Site Admin can be given restricted or full access to the site. They can:

* Arm and disarm the system remotely, for the areas they have privileges for.
* Gain access through doors they have privileges for.
* Start the door unlock schedule by being the first to request access at the door during the period it is scheduled to be unlocked.

They can also be given the following privileges by a Site Manager:

* Remote lock/unlock doors to selected areas.
* Remote arm/disarm selected areas.

Without the above two privileges the use must be onsite and at a reader to complete the actions.

### Site Member <a href="#site-member" id="site-member"></a>

The Site Member is the most limited user role. They can access a locked door only if the site is already disarmed.

[<br>](https://help.security.gallagher.com/smb-installer-portal/gallagher-smb-customer-app/managing-users/delete-or-disable-a-user)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.security.gallagher.com/smb/smb-app/team/user-privileges.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.