> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/command/users-and-permissions/roles-and-permissions-for-command/customize-roles-and-permissions.md).

# Modify Default Roles

Verkada's standard site roles (Site Admin and Site Viewer) include a set of default permissions. Organization Admins can extend or restrict those defaults to match their organization's needs without creating a new role from scratch.

***

## Configuration

{% hint style="danger" %}
You need [Org Admin](/command/users-and-permissions/roles-and-permissions-for-command.md) permissions to customize roles and permissions.
{% endhint %}

{% stepper %}
{% step %}
**In Verkada Command, go to All Products > Admin.**
{% endstep %}

{% step %}
**Under Admin > Users & Permissions, toggle on Customize Roles.** 

This may take a few minutes to update.

{% hint style="info" %}
Enabling this feature unlocks Custom Roles, which let you create new roles with fully customized permission sets. See [Custom Roles](/command/users-and-permissions/roles-and-permissions-for-command/custom-roles.md) for more information.
{% endhint %}
{% endstep %}

{% step %}
**After the feature has been enabled. You can navigate to** **Admin > Users & Permissions > Modify Default Roles.**
{% endstep %}

{% step %}
**Under Modify Default Roles:**

a. Click **Edit** next to a role and configure permissions as needed.\
b. Click **Save.**
{% endstep %}

{% step %}
**(Optional) Toggle on Global Site Admin to automatically grant Org Admins Site Admin permissions for all sites.**
{% endstep %}
{% endstepper %}


---

# 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.verkada.com/command/users-and-permissions/roles-and-permissions-for-command/customize-roles-and-permissions.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.