Create a resource set
Create a collection of your org's user groups, workflows, authorization servers, apps, and customizations. After you've created a resource set you can assign it to the admins and roles in your org.
Before you begin
-
Ensure that you're signed in as a super admin.
Start this task
- In the Admin Console, go to .
- Go to the Resources tab. The Resources tab displays a list of previously created resource sets and their descriptions. You can also edit the resource set from this page.
- Click Create new resource set. The Create new resource set page opens.
- In the Name field, enter the name of the resource set. Choose a name that describes the resources it includes.
- Optional. In the Description field, enter a short description of the resource set.
- Click Add Resources and select one or more resources.
- Click Save selection. You can see the resource set you just created on the Resources tab.
Resource type |
Resource |
Value |
Comments |
---|---|---|---|
Users |
Add users from the following groups or realms |
Enter group names or realm names to add all users from those groups. |
Select Constrain to all users if you want the resource to be constrained to all users in the organization. Remember, when you constrain these resources to a role, the user permissions of the role will impact the resources and the admin can manage the users within the groups selected here. See Role permissions. Realms is an early access (EA) feature. Early Access release. See Enable self-service features.
|
Groups |
Add groups |
Enter group names to constrain the resource to admins. |
Select Constrain to all groups if you want the resource to be constrained to all groups in the organization. When used in an admin assignment that has group permissions in the role, this constrains what groups the delegated admin has group permissions on. See Role permissions. |
Applications |
Add applications |
Enter application names to constrain the resource to admins. |
You can add apps and app instances as a resource. The resource will apply to all application and profile source permissions. See Best practices for creating a custom role assignment. Select Constrain to all applications if you want the resource to be constrained to all applications in the organization. You can select the app type (such as all Salesforce apps) or specific app instances. |
Workflows |
Add delegated flows |
Enter workflow names to constrain the resource to admins. |
Select Constrain to all delegated flows if you want the resource to be constrained to all delegated flows in the organization. |
Customizations |
All customizations | n/a |
These admins can create and delete brands, add and manage custom domains, add and manage email domains, manage SMS, and configure general customization settings. |
Authorization server |
Add authorization servers |
Enter authorization server names to constrain the resource to admins. |
Select the Constrain to all authorization servers check box if you want the resource to be constrained to all authorization servers in the organization. Admins can create new authorization servers only if their role is scoped to all authorization servers. |
Support cases | All cases opened by the admin | n/a |
These admins can manage the support cases that they've opened. Early Access release. See Enable self-service features. |
Identity providers | All IdPs | n/a |
These admins can add and manage all IdPs. |
Devices | All devices | n/a |
These admins can manage and view all devices. See Device lifecycle for more information about the operations that can be performed on devices. Early Access release. See Enable self-service features. |
Identity and access management |
All identity and access management resources | n/a |
These admins can view roles, resources, and admin assignments in the organization. Early Access release. See Enable self-service features. |
Realms |
Add user from all realms or a specific realm | Select all realms or select a specific realm. |
Early Access release. See Enable self-service features. |
You can use Okta-sourced, AD-sourced, and LDAP-sourced groups as resources. However, the following permissions aren't applicable to AD-sourced and LDAP-sourced groups:
- Create users
- Manage users' authenticator operations
- Edit users' profile attributes
- Manage group membership