> 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/access-control/users-and-credentials/add-and-modify-access-groups/use-scim-for-access-groups.md).

# Use SCIM for Access Groups

Learn how to use SCIM to add users to access groups

{% hint style="info" %}
If your organization uses Directories for Access Control, see [Manage Users with Directories](/command/users-and-permissions/manage-users-in-your-organization/directories-for-user-group-management.md) before making changes. It explains how Directories affect where users are managed and what permissions apply.
{% endhint %}

You can use System for Cross-Domain Identity Management (SCIM) to add users to access groups.

{% hint style="warning" %}
The steps in this article only work once your SCIM users and groups have been provisioned to Verkada Command.
{% endhint %}

***

## Add users to access groups

{% hint style="danger" %}
You must create users and assign users to groups in your SCIM provider. The process differs based on your provider, where both Okta ([SAML](/command/security/identity-providers/okta.md) and [SCIM](/command/security/identity-providers/okta.md)) and Microsoft Entra ID ([SAML](/command/security/identity-providers/microsoft-entra-id.md) and [SCIM](/command/security/identity-providers/microsoft-entra-id.md)) are supported.
{% endhint %}

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

{% step %}
**On the left panel, click Access Users and Groups.**
{% endstep %}

{% step %}
**At the top, click Groups > Create SCIM Group.**
{% endstep %}

{% step %}
**Filter or select the SCIM group you want to automatically create a new access group with the name of your SCIM group.**
{% endstep %}

{% step %}
**Click Done.**
{% endstep %}
{% endstepper %}

Your SCIM group has now become an access group. Now, you can assign this group [access levels](/access-control/access/add-and-modify-access-levels/access-level-schedules-and-exceptions.md) to give users in this group access to doors.

{% hint style="warning" %}
If the SCIM provider is unlinked from your Verkada Command organization, all SCIM access groups will be deleted.
{% endhint %}

***

{% hint style="info" %}
**Prefer to see it in action?** Check out the [video tutorial](https://www.youtube.com/watch?v=YSMzqFwWlW4).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.verkada.com/access-control/users-and-credentials/add-and-modify-access-groups/use-scim-for-access-groups.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.