> For the complete documentation index, see [llms.txt](https://docs.txn.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.txn.io/getting-setup/back-office-user-roles.md).

# Back office user roles

Merchants can have multiple users in their Txn back office. Users with the Owner role manage them on the **Team** page: **Add User** sends an invitation (first name, last name, email and role), and **Edit** changes a user's role or status. Inviting and editing users asks for the 6-digit code from the Owner's authenticator app. An invitation is valid for 48 hours. Owners can suspend a user and reactivate them later. API keys and webhooks (**Developer Tools**) are available to Owners only.

<table data-full-width="false"><thead><tr><th>User Role</th><th>Manage API keys</th><th>Manage users</th><th>Withdraw funds</th><th>Exchange funds</th><th>View transactions</th></tr></thead><tbody><tr><td>Owner</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td><td>✓</td></tr><tr><td>Spender</td><td>—</td><td>—</td><td>✓</td><td>✓</td><td>✓</td></tr><tr><td>Trader</td><td>—</td><td>—</td><td>—</td><td>✓</td><td>✓</td></tr><tr><td>Viewer</td><td>—</td><td>—</td><td>—</td><td>—</td><td>✓</td></tr></tbody></table>


---

# 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.txn.io/getting-setup/back-office-user-roles.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.
