> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/transfer-others-permission.md).

# Permission to Transfer Others' Conversations

Explicitly authorize support agents to transfer conversations that other agents are handling, and understand what each role can do with their own, colleagues', and unassigned cases.

The <mark style="color:blue;">Transfer Others' Conversations Permission</mark> determines whether a member can transfer conversations that other support agents are currently handling to someone else. It is a standalone action permission, managed separately from whether a member can open the <mark style="color:blue;">Customer Service Conversations</mark> page or access the conversation platform.

## When to configure it <a href="#when-to-configure" id="when-to-configure"></a>

A support supervisor who is an organization owner wants regular support agents to be able to transfer the cases they handle, but not reassign cases that their colleagues are handling. The supervisor clears the <mark style="color:blue;">Transfer Others' Conversations Permission</mark> from the regular support agent role. Regular agents can still transfer their own conversations, while the supervisor can help dispatch conversations across colleagues.

## Configure a role's permissions <a href="#configure-role" id="configure-role"></a>

1. Open <mark style="color:blue;">Organization Settings</mark> → <mark style="color:blue;">Organization Overview</mark>, and click <mark style="color:blue;">Edit Role Permissions</mark> under <mark style="color:blue;">Management Actions</mark>.
2. Edit the role you want to adjust and open the <mark style="color:blue;">Role Permissions</mark> tab.
3. Under <mark style="color:blue;">Customer Service Conversation Permissions</mark>, select or clear <mark style="color:blue;">Transfer Others' Conversations Permission</mark>, then click <mark style="color:blue;">Save</mark>.
4. Check the member's default role and any other custom roles: as long as any one role still has this permission, the member can still transfer other agents' conversations. Ask the member to refresh the page and confirm.

<figure><img src="https://1360999650-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6v6TNkkOQVfRYfcNirHL%2Fuploads%2Fgit-blob-2a4a33488b7a998a3acbca807b04d849d6db758b%2Frole-transfer-others-permission.png?alt=media" alt="The All Conversations permission and the Transfer Others&#x27; Conversations Permission checkboxes under Customer Service Conversation Permissions"><figcaption><p>The Transfer Others' Conversations Permission is a standalone action permission, selected separately from the All Conversations permission</p></figcaption></figure>

{% hint style="warning" %}
Organization owners always have this permission. To restrict regular members, verify with a regular member's account; clearing the checkbox on one custom role does not remove a permission granted by another role. New roles do not have this option selected by default, so grant it explicitly based on job needs. Selecting this option alone does not grant access to the Customer Service Conversations page or the conversation platform; it must be selected explicitly and cannot be granted by relying on a parent-level permission.
{% endhint %}

For other role and resource settings, see [Role Permission Management](https://docs.maiagent.ai/maiagent-user-guide/en/org/roles/role-permission.md).

## What support agents can do in a conversation <a href="#conversation-actions" id="conversation-actions"></a>

| Who is currently handling the conversation            | Is the Transfer Others' Conversations Permission required?                                                           |
| ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
| Yourself                                              | No; you can still <mark style="color:blue;">Transfer</mark> to a colleague                                           |
| Another support agent                                 | Yes; without the permission, the <mark style="color:blue;">Transfer</mark> button is not shown for that conversation |
| No human agent (handled by AI, queued, or unassigned) | No; you can still <mark style="color:blue;">Take Over</mark> or <mark style="color:blue;">Assign Agent</mark>        |

If the permission is revoked while the screen is open, or the conversation you were about to take over has just been picked up by another agent, the action may show "You do not have permission to transfer others' conversations"; the conversation stays with its current owner, so please recheck the latest status. This permission does not affect other existing actions such as <mark style="color:blue;">Resolve</mark> and <mark style="color:blue;">Return to AI Agent</mark>.

{% hint style="info" %}
To get help transferring another agent's case, ask an organization owner or a member who has this permission. Access to the Customer Service Conversations page and the conversation platform must still be granted separately. For the full steps on taking over, transferring, and returning a conversation to AI, see [Human Agent Handoff and Replies](https://docs.maiagent.ai/maiagent-user-guide/en/serve/daily-operations/human-handoff-operations.md#transfer-and-return).
{% 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://docs.maiagent.ai/maiagent-user-guide/en/org/roles/transfer-others-permission.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.
