---
schema_version: "1"
id: 3cb6feaedce88f1e1d214f6ef19eb5109de5e9277ffce5a739d285f4d64fefcc
title: Collaborating with External Partners 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_collaborating_with_external_partners.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.automate_afsc_collaborating_with_external_partners.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 47e593b833b02f5834c16d2337664101abbb13f2ba8e46091b7222302db23937
description: 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.
products:
  - Cross Cloud
release: "264"
---
# Collaborating with External Partners in Agentforce Operations

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.

### 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="d20250e37">License Required</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="License Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d20250e37 ">
            <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>

## Internal Users Compared to External Users

Every user in an Agentforce Operations workspace has a user type: internal or external. The user type controls what a user can see and do in the workspace.

Internal users

Typically employees of your organization. Internal users can see the identities of all other users in the workspace, see all unrestricted data (such as data source contents and the catalog of defined integrations), and can have view or edit access levels on resources, such as blueprints or workflows. Internal users can have any system or custom role.

External users

Typically suppliers, vendors, or other partners. External users have restricted visibility in the workspace and can't have system roles. They can view workflows and tasks you've given them explicit access to, but they can't view blueprints or the full list of people in the workspace. External users can join teams.

## What External Users Can Do

- Complete tasks through email or web forms without signing in.
- Log in to the workspace to view and complete tasks you've assigned to them.
- Comment on tasks you've assigned to them or cc'd them on.
- Have custom roles.

## What External Users Can't Do

- See unrestricted data in the workspace, such as the full catalog of data sources or integrations.
- Have system roles, such as Admin, Creator, Publisher, Data Source Admin, Integration Admin, or People Admin.
- Have edit access to workflows or blueprints.
- See other users in the workspace unless they have an association with them.

## User Association and Visibility

External users represent external parties such as potential suppliers, so it's crucial that they can't discover each other in the workspace. External users can see or query for another user only if they have an association with them.

Two users have an association in either of these cases:

- **Previous collaboration**: You've assigned both users to the same task or cc'd them on the same task.
- **Matching email domains**: Their email addresses share the same domain.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-agentforce_operations-264-0-0-production-enus/dce314e6-0a31-4a8b-98f7-3d2a3fd02ee2/images/icon_important.png)

Important If you don't account for email domain matching, you can create unwanted inter-user visibility:

- If multiple external suppliers have email addresses at a public domain like `gmail.com`, Agentforce Operations treats them as associated, so they can see each other.
- If your business practices involve creating email addresses at one of your own domains for external suppliers, those suppliers can see any other users in the workspace who share that email domain.

When you grant an external user access, use distinct domains for each supplier organization whenever possible.

## Ways External Users Complete Work

External users can participate in workflows through multiple channels:

Email

Reply to the notification email to complete tasks, post comments, approve or reject approval tasks, or attach files. External users can click action buttons in the email body without signing in.

Web form

For tasks that require complex structured data, external users receive a **Complete Form** link in an email. The link opens a restricted browser view where they can complete the form. Agentforce Operations uses device verification for security, and limits the external user's access to reading and writing data only for that specific form.

Workspace

External users can log in to the workspace to view and complete the tasks you've assigned to them. They can see only the workflows and users that they have an association with.