How to Allow Company Users to Open Veeam Backup & Replication Web UI Wizards From Veeam Service Provider Console
| KB ID: | 4908 |
| Product: | Veeam Service Provider Console | 9.3 |
| Published: | 2026-09-01 |
| Last Modified: | 2026-09-01 |
Oops! Something went wrong.
Please, try again later.
Purpose
This article documents how to allow company users to open Veeam Backup & Replication web UI wizards from Veeam Service Provider Console for backup servers managed by their company.
Starting with Veeam Service Provider Console 9.3, users can perform restore operations by redirecting to the Veeam Backup & Replication web UI wizards from Veeam Service Provider Console. For details, see the Restoring Veeam Backup & Replication Workloads section of the Veeam Service Provider Console Guide for Service Providers.
Access to the wizards depends on the user type:
- Service provider users: The wizards are available by default.
- Company users: The wizards are disabled by default and must be explicitly enabled using the configuration key described in this article.
- Reseller users: The wizards are not available, regardless of the configuration key.
If a company user attempts to open a Veeam Backup & Replication web UI wizard while the key is disabled, the operation fails with the following error:
Cannot open the Veeam Backup & Replication wizard because this capability is not enabled for your organization. Contact your service provider for assistance.
The configuration key described in this article affects the Veeam Backup & Replication web UI wizards only. It does not affect redirecting to the Veeam Backup & Replication web UI itself, which remains available to service provider users only.
Solution
To allow company users to open Veeam Backup & Replication web UI wizards, add a configuration key on the machine where the Veeam Service Provider Console Server component is installed:
- Open the following file in a text editor:
C:\ProgramData\Veeam\Veeam Availability Console\Configuration\Service\configuration.overrides.json
The same folder can also contain incremental configuration files namedconfiguration.overrides.NNNNNNNN.json. Those files are generated and merged automatically, and should not be edited manually. - Add the following key inside the root JSON object (or change its value if the key is already present):
"ClientAgent_TreatClientAgentsAsCompanyOwned": "true"
Key Name: ClientAgent_TreatClientAgentsAsCompanyOwned
Value Type: Boolean
Value Data:
true — company users can open Veeam Backup & Replication web UI wizards for backup servers managed by their company.
false — the functionality is available to service provider users only.
Default: false - Save the file. The configuration file is monitored for changes, so a short delay can occur before the change is applied.
- Restart the Veeam Management Portal Service (service name:
VeeamManagementPortalSvc).
The service can be restarted using the following PowerShell command:
To revert to the default behavior, set the key value to false (or remove the key) and restart the service.
Regardless of this configuration key, the Enable redirecting to Veeam Backup & Replication web UI wizards toggle must be enabled for the backup server, and the company user must have a role that permits the corresponding restore operations, such as Company Owner or Company Administrator. For details, see the Configuring Remote Access section of the Veeam Service Provider Console Guide for Service Providers.
More Information
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please, try again later.