Overview
Combine scopes with the default user permissions and roles to create custom data views. Scopes allow the administrator to provide access to each site or brand's information separately.
Create new scopes
Scopes are expressions used to identify what kind of data will be displayed to users.
- Go to Account Settings > Scopes > Create New Scope.
- Name and customize your scope. You can find examples below.
- Click Save.
Scope examples
When creating scopes, use the +Value, +Add, and +Or options to make your scope's expression more complex and targeted. Each example below reviews how these options can build on each other to create a more specific experience for your users. The examples also assume you will be applying the scope to all of the user's roles.
+Value considers additional values in an individual rule. This example used +Value to create a scope for host names. Users would only be able to access data related to abc.com or def.com.
+And requires multiple rules to be considered at once. This example used +Add with +Value for the mobile-centric data of several host names. Users would not be able to access data related to other host names or devices.
+Or considers a completely separate rule. This example used +Or with the previous ruleset for the mobile-centric data of abc.com and def.com or all the data related to ghi.com.
Modify existing scopes
- Go to Account Settings > Scopes.
- Click the name of the scope you wish to edit.
- Click Edit.
- Make the desired changes.
- Click Save.
Apply scopes to users
- Go to Account Settings > Users & Permissions.
- Use the search bar or manual review to locate the desired existing user.
- Select the Edit icon by the user's name.
- Add the scope to the desired user roles. The scope's restriction will only affect the data associated with each role.
- Click Save.
You can also apply scopes when creating a new user.
Delete scopes
- Go to Account Settings > Scopes.
- Click the name of the scope you wish to edit.
- Click Delete.
- Click Delete again to confirm the removal.
Article is closed for comments.