This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Policy sets
Policy sets are objects in Citrix DaaS which aggregates policies to allow for simplified, role-based access, and easy management. You can create policy sets to mirror logical divisions in your administrator team and company. For example, you can create a policy set for each geographic region, business-unit, or for specific use case. Once created, scopes and delivery groups are assigned to policy sets so that only authorized administrators can manage the policies that apply to their relevant users and machines.
Benefits
- Role-based access control for distributed administrator teams
- Simplified mergers, acquisitions, and consolidations
- Limited fault domain
- Multitenant support for policies
Enable policy sets
From Studio, navigate to Settings and turn on the Policy sets setting.
Note:
You must enable policy sets before creating a policy set.
Feature comparison
Before applying policy sets | After applying policy sets |
---|---|
Policies, settings, filters, and policy priorities for the entire site are configured in one place within Citrix Studio. | Policies, settings, filters, and policy priorities are configured separately for each policy set. |
If you manage one policy, you must manage every policy. | Full administrators can delegate to lower-level admins the ability to manage a particular policy set on an individual basis. |
Policies in large and distributed environments become complex and difficult to manage. | Policies in large and distributed environments can be divided and managed easily. |
How do policy sets work?
General overview
- Policy sets are assigned to delivery groups
- Policy sets have one or multiple scopes
- Delivery groups with no policy set assigned receive the default policy set
- A delivery group can have only one policy set assigned to it
- Multiple delivery groups can use the same policy set
- Even though policy sets are assigned to delivery groups, the policies maintain their filters
For more information, see How do filters get applied?. There is no change in the way that policy assignments or policy filters work for policy sets. That is, they work the same way as they do for policies.
Default policy set
- When the policy set setting is turned on, all existing policies are grouped within the default policy set
- Every delivery group receives the default policy set unless the administrator team creates a policy set and assigns that to a delivery group.
- Once a delivery group has a different policy set assigned to it, it will no longer get policies from the default policy set
Policy set creation
Policy sets can be created in the following two ways:
- Create policy set - this action creates an empty policy set
- Clone policy set - this action creates a policy set based on an existing policy set
Create policy sets
- From Studio, select the Policies node in the left pane.
-
Click the Policies tab.
- Select Create Policy Set. The Introduction tab appears.
- Click Next or click Name and Description tab.
- Enter the name and description of the policy set.
- Click Next or click the Assignments tab.
- Select one or more delivery groups to which you want to assign the policy set.
- Click Next or click Scopes tab.
- Select the scopes of the policy set.
- Click Create. The policy set is created with the defined assignment and scope.
Clone policy sets
- From Studio, select the Policies node in the left pane.
- Click the Policies tab.
- Select Clone Policy Set.
- Modify the name of the policy set.
- Modify or create assignments for the policy set and click Next.
- Select or deselect policies to include in the cloned policy set.
- Modify the scope of the policy.
- Click Create. The policy set is created.
Edit policy sets
- From Studio, select the Policies node in the left pane.
- Click the Policies tab.
- Select Edit Policy Set.
- Modify the name of the policy set and click Next.
- Modify or create assignments for the policy set and click Next.
- Modify the scope of the policy.
- Click Create.
Policy set assignment
Policy sets are assigned to delivery groups. You can configure assignments when the policy set is created or edited. You can also configure assignments when delivery groups are created or edited.
Policy set scopes
Administrators can define the scope of the policy set so that only authorized administrators can view or edit it. You can configure scopes when the policy set is created or edited.
With the introduction of Policy Sets, you can also create and manage Citrix Policy using API. For more information, see How to create a policy set in Citrix DaaS.
Share
Share
In this article
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.