> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/tcs-client/user-management/user-roles-and-permissions.md).

# User Roles and Permissions

The user roles in TCS and what each one can see and do.

{% hint style="info" %}
**Use this when** you want to know what each TCS user role can do before creating a user.
{% endhint %}

When you order the service, Verifone gives login details to **one person** chosen by your company. This is the **root user**. The root user can create more accounts for other people, who become **sub-users**.

TCS has **five user roles**:

| Role                                     | What they can do                                                                                                    | Tabs they can see                                                   |
| ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
| **Manager**                              | Full rights. Note: only the root user can approve their own refund requests.                                        | All tabs                                                            |
| **Read only**                            | View reports, payment terminals, and refund requests.                                                               | Home, Clearing Status, Reports, Refund requests, Search             |
| **Confirm issues and void transactions** | View reports, confirm issues, refunds, and view payment terminals.                                                  | Home, Clearing Status, Reports, Management, Search, Refund requests |
| **Confirm issues and request refunds**   | View reports, confirm issues, request refunds, approve refund requests (not their own), and view payment terminals. | Home, Clearing Status, Reports, Refund requests, Search             |
| **User management only**                 | Create and delete users.                                                                                            | User management                                                     |

To add a user, see [How to Create a User](/support-nordics/tcs-client/user-management/how-to-create-a-user.md).

<details>

<summary>Keywords</summary>

Also called: user roles, permissions, access rights, root user, sub-user. Search terms: user roles, permissions, root user, manager, read only, user management, rights.

</details>


---

# 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.verifone.com/support-nordics/tcs-client/user-management/user-roles-and-permissions.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.