You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. Click **Next** to open the **Resource roles** tab.
99
+
7. Click **Next** to open the **Resource roles** tab.
100
100
101
101
On this tab, you select the resources and the resource role to include in the access package.
102
102
103
-
1. Click **Groups and Teams**.
103
+
8. Click **Groups and Teams**.
104
104
105
-
1. In the Select groups pane, find and select the **Marketing resources** group you created earlier.
105
+
9. In the Select groups pane, find and select the **Marketing resources** group you created earlier.
106
106
107
107
By default, you see groups inside and outside the **General** catalog. When you select a group outside of the **General** catalog, it will be added to the **General** catalog.
> When using [dynamic groups](../users-groups-roles/groups-create-rule.md) you will not see any other roles available besides owner. This is by design.
On this tab, you create a request policy. A *policy* defines the rules or guardrails to access an access package. You create a policy that allows a specific user in the resource directory to request this access package.
120
124
121
-
1. In the **Users who can request access** section, click **For users in your directory** and then click **Specific users and groups**.
125
+
13. In the **Users who can request access** section, click **For users in your directory** and then click **Specific users and groups**.
0 commit comments