> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://support.atomicwork.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://support.atomicwork.com/_mcp/server.

# Provisioning methods for entitlements

> Choose how access to an entitlement is granted and revoked: add the user to an IdP group, run a code script, or assign the access request to a group or agent.

Every entitlement has a **provisioning action** (how access is granted) and a **de-provisioning action** (how access is revoked). When an employee's access request is approved, the **AccessOps Manager** coworker carries out the provisioning action you set here.

Not every app has an identity provider (IdP) group behind it. Besides IdP groups, you can grant and revoke access by running a script from your Code library, or by assigning the access request to a group or agent.

You pick the method from three tabs:

| Tab                  | Methods                                                                          | Use it when                                                            |
| -------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------- |
| **Add to IdP group** | **Add to Okta group**, **Add to Entra group**, **Add to Google Workspace group** | The app's access is managed through an IdP group.                      |
| **Custom action**    | **Run code script**                                                              | The app has an API but no IdP group. A published script calls the API. |
| **Assign ticket**    | **Assign to group**, **Assign to agent**                                         | A team, a person or an AI Coworker should fulfill the request.         |

## Before you begin

* **Permissions:** You need permission to manage applications (**Settings > Access management > Applications**).
* **AccessOps Manager:** The **AccessOps Manager** coworker must be published. See [Setting up agentic access provisioning](/documentation/identity-access-management/access-management/setting-up-agentic-access-provisioning).
* **For Run code script:** The script must be **published** in the Code library. See [Code library](/documentation/ai-workforce/code-library).
* **For Assign ticket:** The group or agent must be in the workspace you pick.

## Open an entitlement's provisioning settings

1. Go to **Settings > Access management > Applications** and open an app from the **Managed** tab.
2. Open the **Entitlements** tab and click an entitlement. To create one, click **Add**.
3. In the **Edit entitlement** dialog, fill in **Basic details**, then go to **Provisioning**.
4. Under **Provisioning action**, open **Method**. Pick a tab, then pick a method. You can also search.

## Grant access with a code script

Use this for apps you can reach through an API but that have no IdP group, such as internal tools or SaaS apps without a connector.

#### Choose Run code script

On the **Custom action** tab, pick **Run code script** ("Grant access by running a published code script.").

![Custom action tab in the Method picker, showing Run code script](/_fern-files/_img/9c24145ad264530630ab58b49960f44553a9c520220e6512cb9de5cb8e16ad76.webp)

#### Pick the script

Under **Code script**, pick a published script from your Code library.

#### Choose how access is revoked

Leave **De-provisioning action is same as the provisioning action** selected to revoke with the same script, or clear it to choose another method. See [Set a separate revoke method](#set-a-separate-revoke-method).

#### Collect information (optional)

Under **Collect information (optional)**, click **Add a question** for anything the requester needs to tell you, such as a team name or a license tier.

#### Save

Click **Save**.

![Run code script with a script selected and the de-provisioning checkbox selected](/_fern-files/_img/e906bdff556344143d91257a4c83b63b23b5b26e6fab6ea69dbf08be5cbff96d.webp)

> **Tip**
>
> If you keep **De-provisioning action is same as the provisioning action** selected, write the script so it handles revoking as well as granting. Atomicwork doesn't undo a script's changes on its own.

To keep secrets out of your script, see [Use saved credentials in code](/documentation/enterprise-workflows/actions-and-integrations/use-saved-credentials-in-code).

## Grant access by assigning the access request

Use this when a team, a person or an AI Coworker should do the provisioning.

#### Choose a method

On the **Assign ticket** tab, pick one:

* **Assign to group**: "Assign the access request to a group for fulfillment."
* **Assign to agent**: "Assign the access request to an agent for fulfillment."

![Assign ticket tab in the Method picker, showing Assign to group and Assign to agent](/_fern-files/_img/8f68dc1661c518efc67af167897fe01dd813d4e3e98b479f7a57f48d491dc705.webp)

#### Pick the workspace and target

Pick the **Workspace**, then the **Group** or agent in that workspace.

#### Choose how access is revoked, then save

Set the de-provisioning action, add any **Collect information (optional)** questions and click **Save**.

![Assign to group for provisioning and de-provisioning, each with a workspace and group](/_fern-files/_img/c9b36267124b2c3a15d0ae2b016ae170d9835f687c1fa19d04b6e6c89617eefe.webp)

When a request for the entitlement is approved, the access request is assigned to the group or agent you picked so they can fulfill it.

## Set a separate revoke method

Clear **De-provisioning action is same as the provisioning action**. A **De-provisioning action** section appears with the same choices:

* **Remove from IdP group**
* **Custom action**: **Run code script** ("Revoke access by running a published code script.")
* **Assign ticket**: **Assign to group** or **Assign to agent**, which assign the revocation request

For example, you can grant access with a script and remove it from an Entra group.

![Separate De-provisioning action: grant with a code script, revoke by removing from an Entra group](/_fern-files/_img/258b998cc1273b2a5213825fb82df8951c979e9762ba8b773a971c4f3b91548a.webp)

## Set methods with AI Assist

You can also ask **AI Assist** to set how an existing entitlement is granted or revoked. It can set **Run code script**, **Assign to group** and **Assign to agent**, and asks you to confirm before it makes the change. To use an IdP group, set it in the entitlement dialog. See [AI Assist](/documentation/ai-knowledge/ai-assist).

## Good to know

* **Existing entitlements keep working.** Entitlements set up before these methods were added keep their current configuration.
* **Pending requests use the current method.** If you change an entitlement's method, requests still waiting to be fulfilled use the new one.

## Related articles

* [Setting up agentic access provisioning](/documentation/identity-access-management/access-management/setting-up-agentic-access-provisioning)
* [Just-in-Time access management](/documentation/identity-access-management/access-management/just-in-time-access-management)
* [Provisioning access with custom workflows](/documentation/identity-access-management/access-management/provisioning-access-with-custom-workflows)
* [Code library](/documentation/ai-workforce/code-library)
* [Code actions](/documentation/enterprise-workflows/actions-and-integrations/code-actions)