---
schema_version: "1"
id: ba20a28129417b9227ab054acdb2c00b862b69d65f5a5428b6be475baafe88e8
title: User Roles and Access Levels in Agentforce Operations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/automate_afsc_roles.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_roles.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 733849c01c59d041a5d5ea685dc28b11c1fcf9f667de75797ecbbd157aef1556
description: Assign specific roles to users that define what they can do in Agentforce Operations. You can use the system roles, or create custom roles. Grant granular access levels to blueprints and workflows.
products:
  - Cross Cloud
release: "264"
---
# User Roles and Access Levels in Agentforce Operations

Assign specific roles to users that define what they can do in Agentforce Operations. You can use the system roles, or create custom roles. Grant granular access levels to blueprints and workflows.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col>
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d33196e41">License Required</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d33196e41 ">
              <p>This feature is a workspace that’s external to your Salesforce org and requires
                an Agentforce Operations license. </p>
              <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                executive.</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:left;vertical-align:top;" id="d33196e75">Role or Access Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d33196e75 ">To add and assign roles in Agentforce Operations:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d33196e75 ">Admin role or People Admin role</td>

          </tr>
          <tr class="">
            <td data-label="Role or Access Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d33196e75 ">To use a role in a blueprint or workflow to grant permissions in Agentforce Operations</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d33196e75 ">Admin role, Creator role, or Edit access for the blueprint or workflow.</td>

          </tr>
        </tbody>
      </table>

## About System Roles in Agentforce Operations

Agentforce Operations comes with a set of system roles you can assign to users. Use the system roles for common access patterns, or create custom roles when you want more granular control.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
          <colgroup>
            <col>
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="colgroup" class="slds-cell-wrap" colspan="1" style="text-align:left;vertical-align:top;" id="d33196e139">License Required</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d33196e139 ">
                <p>This feature is a workspace that’s external to your Salesforce org and requires
                  an Agentforce Operations license. </p>
                <p style="margin-bottom:0;">To purchase an Agentforce Operations license, contact your Salesforce account
                  executive.</p>
              </td>

            </tr>
          </tbody>
        </table>

Users can be assigned to multiple roles. Internal users can be assigned any system or custom role. External users can be assigned to only custom roles. Learn more about external users in [Collaborating with External Partners in Agentforce Operations](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_collaborating_with_external_partners.htm&release=264.0.0&type=5 "Invite suppliers, vendors, and other external partners to participate in your workflows in Agentforce Operations. External users can complete tasks through email, forms, or the workspace, with visibility restrictions that protect workspace data.").

Role assignment controls workspace capabilities. Blueprint-level and workflow-level access is configured separately.

Task assignment grants task-level access only. If an assignee needs to view the full workflow, grant them workflow-level access from the Access tab.

### System Roles That Come with Agentforce Operations

System Roles in Agentforce Operations  
| Role | Access Description |
| --- | --- |
| Admin | Full access to all features, settings, and data |
| Creator | Build blueprints, forms, and fields |
| Data Source Admin | Create and manage data sources in the workspace |
| Integration Admin | Create and manage integrations |
| People Admin | Manage people, teams, and roles |
| Publisher | Publish blueprints |

## Create Custom Roles for Blueprint or Workflow Access

Create custom roles to grant blueprint or workflow access levels for users.

With custom roles, you can grant specific blueprint or workflow access levels for users. Unlike system roles, custom roles are limited to these and can’t modify other workspace settings.

1. In the navigation sidebar, click **Admin**.
2. Click the **Roles** tab.
3. Click **\+ Add role**.
4. Enter a name for the role.
5. If you want users assigned to this role to be able to add users to the workspace, select **Allow inviting people to the workspace**.
6. Click **Add**.
    
    The role is created but without granting any access level. To add blueprint or workflow access levels to a custom role, grant access from the blueprint or from the workflow's Access tab.

## Assign Blueprint and Workflow Access Levels in Agentforce Operations

Get granular access control by setting access rights for each blueprint and workflow in Agentforce Operations.

Task assignees and CC'd users appear in the Access tab with no access by default. No access means they can see and complete only their assigned tasks, not the full workflow details. To give a task assignee or CC'd user workflow-level access, grant it explicitly in the workflow's Access tab or through a team or role assignment.

1. [Create a blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_create_blueprint.htm&release=264.0.0&type=5 "Use AI to generate a blueprint by describing your process and optionally uploading supporting documents. You can also build a blueprint from scratch or import one from another workspace. Anyone with the Creator role can generate blueprints in Agentforce Operations.") or [edit an existing blueprint](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_edit.htm&release=264.0.0&type=5 "Open an existing blueprint for editing to add stages, tasks, automations, or other changes.").
2. In the draft blueprint, click the **Access** tab.
3. To grant blueprint access levels:
    1. In the Blueprint access section, click **+Grant access**.
        
        You can't grant access to a published blueprint. Create a new blueprint version and then select the access level for the new version.
    2. For **People**, select the person, team, or role to grant access to.
    3. For **Configure access**, select the access level.
        
        Blueprint Access  
        | Access Level | Description |
        | --- | --- |
        | Draft blueprint: None | No access to the draft blueprint. |
        | Draft blueprint: View | View but not edit the specified draft blueprint. |
        | Draft blueprint: | Make edits to the specified draft blueprint. |
        | Published blueprint: View | Open and view the full details of the specified published blueprint. |
        | Published blueprint: Start workflows | Start workflows from the specified published blueprint. |
        | Published blueprint: Create variants | Create variants of the specified blueprint. Also grants View access to the published blueprint. This option shows only after you [enable variants](https://help.salesforce.com/s/articleView?id=platform.automate_afsc_blueprints_variants_enable_create.htm&release=264.0.0&type=5 "Turn on variants for a blueprint to collect the same data but run different stages and tasks based on conditions you define in Agentforce Operations. Then create, update, and unlink variants as needed.") on the draft blueprint. |
4. To grant workflow access levels:
    1. In the **Workflow access** section, click **\+ Grant access**.
        
        The access level granted is for workflows created from the specified blueprint.
    2. For **Grant to**, select the person, team, or role to grant access to.
    3. For **Configure access**, select the access level.
        
        Workflow Access  
        | Access Level | Description |
        | --- | --- |
        | View | View all the details for the specified workflow. |
        | Comment | Make comments on the tasks and work log items for the specified workflow. |
        | Edit | Make edits to the specified workflow. |