Citrix DaaS™

Citrix DaaS™ for Citrix Service Providers

September 19, 2025

Contributed by:

This article describes how Citrix Service Providers (CSPs) can set up and manage multitenant Citrix DaaS environments in Citrix Cloud. It also explains how tenant customers can access and co-manage their assigned environments through delegated administration.

For an overview of the features available for Citrix Partners, see Citrix Cloud for Partners.

The setup and management process involves two key areas:

Manage multitenant DaaS deployments as partner administrators: How CSPs (Partners) configure and manage multitenant DaaS environments in Citrix Cloud.
Manage your DaaS resources as tenant administrators: How tenant customers access and manage their own DaaS resources in cooperation with CSPs under multitenant deployments.

Requirements

To set up and manage a multitenant Citrix DaaS environment in Citrix Cloud™, Partners must meet the following prerequisites:
- Have Citrix Service Provider partner status
- Have a Citrix Cloud™ account.
- Have an active multitenant Citrix DaaS subscription
To manage a tenant’s DaaS resources in a multitenant Citrix DaaS environment, Tenant administrators must meet the following prerequisites:
- Have Citrix Cloud account created by a CSP and added to the CSP’s multitenant DaaS service
- Be assigned a tenant DaaS administrator role

Limitations and known issues

This section outlines the current limitations and known issues in the CSP multitenant DaaS environment.

Limitations

Resource filtering by scope in Studio (similar to Monitor) is not available.
Tip:

To view resources associated with a scope:
1. Select Administrators in the left pane.
2. On the Scopes tab, select the scope and then select Edit Scope in the Action bar.
Alternatively, the partner administrators can sign in to the tenant account to view scoped resources in the tenant Studio console.
Tenant administrators cannot create host connections or manage tags. This limitation is due to zones and tag objects not being scoped.
When onboarding a new tenant, the partner administrator must create the first machine catalog, assign it to a zone, and apply the appropriate scope in the partner’s Studio console. After that, the tenant administrator can create or edit catalogs within the tenant account, based on the zone associated with the first catalog.
Tenant administrators cannot access Workspace Environment Management™ (WEM) configuration sets. A partner administrator must assign the configuration set.
Folders under Machine catalogs are not yet scoped so that aren’t accessible to tenant administrators.

Known issues

The partner Studio console doesn’t automatically enforce scopes. You are responsible for selecting the appropriate scope when creating machine catalogs, delivery groups, and application groups for the appropriate tenant.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Citrix DaaS™ for Citrix Service Providers

September 19, 2025

Contributed by:

September 19, 2025

Contributed by:

Citrix DaaS™ for Citrix Service Providers

Requirements

Limitations and known issues

Limitations

Known issues

In this article