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 — confirm access and readiness
• Schedule rollouts — choose the rollout task