> 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/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/manage-rollouts/user-privileges.md).

# User privileges

Check which roles can create, edit, monitor, or cancel rollout work.

Use this page to confirm which roles can perform rollout actions.

### When to use this page

Check this page before you create a rollout, start a new batch, edit a saved rollout, or cancel a rollout job.

### How to read the matrix

* **Yes** means the role can perform the action.
* **No** means the role cannot perform the action.
* Use the most specific role that matches the user who will perform the task.

### Rollout permissions by role

| Operations                                      | Estate Owner Admin | Reseller Manager | Merchant Admin | Merchant User | Merchant Supervisor | Verifone Admin | Verifone Helpdesk | Partner Helpdesk | Verifone Field Service Provider | Partner Field Service Provider |
| ----------------------------------------------- | ------------------ | ---------------- | -------------- | ------------- | ------------------- | -------------- | ----------------- | ---------------- | ------------------------------- | ------------------------------ |
| View System-Wide Rollout                        | Yes                | Yes              | Yes            | Yes           | Yes                 | Yes            | Yes               | Yes              | No                              | No                             |
| Options > Create New Rollout                    | Yes                | Yes              | No             | No            | No                  | Yes            | Yes               | No               | No                              | No                             |
| System-Wide Rollout > Options > Start new batch | Yes                | Yes              | No             | No            | No                  | Yes            | Yes               | No               | No                              | No                             |
| System-Wide Rollout > Options > Edit batch      | Yes                | Yes              | No             | No            | No                  | Yes            | Yes               | No               | No                              | No                             |
| System-Wide Rollout > Options > Cancel Job      | Yes                | Yes              | No             | No            | No                  | Yes            | Yes               | No               | No                              | No                             |

### Key takeaways

Use these quick rules:

* rollout creation and editing are limited to admin and helpdesk roles listed as **Yes**
* merchant roles can view rollout status but cannot create or edit rollout jobs
* field service provider roles do not manage estate-wide rollout actions

### If an action is unavailable

Confirm that you are using the intended role. Check the matrix for the exact action. Ask an authorized admin or helpdesk role to perform the action when access is not available.

Do not use a different rollout workflow to work around a missing permission.

### Before requesting access

Identify the exact rollout action and estate scope required. A user who can view rollouts may not create, edit, or cancel them. Confirm the role before planning the rollout.

### Related pages

* [Prerequisites](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/manage-rollouts/prerequisites) — confirm access and readiness
* [Schedule rollouts](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/rollouts/schedule-rollouts) — choose the rollout task


---

# 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/verifone-central-getting-started/verifone-central/verifone-central-device-manager/rollouts/manage-rollouts/user-privileges.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.