Roles, permission sets, and model sets are used together to manage what users can do and what they can see. The Roles page in the Users section of the Admin panel lets you view, configure, and assign roles, permission sets, and model sets.

Definitions

• A role defines the privileges that a user or group will have for a specific set of models in Looker. You create a role by combining one permission set with one model set.
• A permission set defines what a user or group can do. You select a combination of permissions that you want to assign to a user or group. It must be used as part of a role to have any effect.
• A model set defines what data and LookML fields a user or group can see. You select a combination of LookML models to which a user or group should have access. It must be used as part of a role to have any effect.

Assigning Roles

A role is a combination of one permission set and one model set. It’s a common convention to name roles after types of people or groups of people in your organization — administrator, Looker developer, Finance team — although you are welcome to follow your own naming conventions.

A user can have more than one role in Looker. This can be useful when you have users who play multiple roles in your company, or when you want to create complex systems of access to your models.

Adding users to multiple roles has important implications for how their permissions are applied. For example, if you allow someone to save_content (an instance-wide permission) in only one of their roles, they will be allowed to save content from any model. In contrast, if you allow someone to access_data (a model-specific permission) in only one of their roles, they can access only the models that are specified in that role.

Multiple roles can also cause unexpected effects on dashboards. See the Managing Business User Features documentation page for information about dashboards and multiple roles.

To create a role, click the New Role button at the top of the Roles page. Looker will display a page where you can enter a name for the role, choose a permission set, and choose a model set. You will also be able to assign the role to a set of users or groups. Once you’ve configured the role as desired, click the New Role button at the bottom of the page.

After a role has been created, you can edit it by clicking the Edit button to the right of the role on the Roles page. This will take you to that role’s page, where you can:

• Rename the role
• Assign or edit the permission set associated with that role
• Assign a model set to the role
• Assign the role to users and/or groups

To delete a role, click the Delete button to the right of the role on the Roles page.

Default Roles

For new instances, Looker creates the following default roles, each of which includes a default permission set of the same name:

• Admin
• Developer
• User
• Viewer

Permission Sets

A permission set defines what a user or group can do. Admins can use Looker’s default permission sets or create original permission sets, keeping in mind permission dependencies.

All the available permissions, and their types, are discussed in more detail below.

Default Permission Sets

For new installations, Looker includes several default permission sets that you can start with:

You’ll see these permission sets appear as options when you create a new role. If you select one of these permission sets, Looker will display the list of permissions it includes.

The Admin permission set cannot be edited or deleted, and cannot be assigned to a role. It is assigned only to the Admin role, which also cannot be edited or deleted. The only way to grant the Admin permission set to a user or group is to add the Admin role to that user or group.

Creating Permission Sets

To create a permission set, click the New Permission Set button at the top of the Roles page. Looker will display a page where you can enter a name for the permission set and select the permissions it should include. Once you’ve configured the set as desired, click the New Permission Set button at the bottom of the page.

After a permission set has been created, you can edit or delete it by clicking the Edit or Delete buttons to the right of the permission set on the Roles page.

Permissions and Dependencies

Some permissions depend on others to work properly. For example, it makes sense that someone who wants to develop in LookML must first be able to see LookML.

When you create a permission set you’ll see the available permissions in an indented list. If a privilege is indented under another (parent) privilege, you must select the parent privilege first. Consider this example:

In this case Looker uses indentation to indicate that:

• The access_data privilege can be selected at any time.
• The see_lookml_dashboards and see_looks privileges require the access_data privilege to be selected first.
• The see_user_dashboards privilege depends on the see_looks privilege, which in turn depends on access_data privilege.

You cannot select a child privilege without first selecting its parent.

Permissions List

The develop and see_lookml permissions interact with model sets in a potentially unexpected way. In Looker’s IDE, a single project can contain multiple model files. If you assign develop or see_lookml to a user, and you’ve allowed that user to see any model that is a part of a project, they will be able to develop or see the LookML for all models in that project. However, they will still not be able to query models that you have not allowed.

Permissions can be classified as one of three types:

• Model Specific: This type of permission is applied only to the model sets that are part of the same role. This permission is applied to individual models or model sets, rather than across the entire Looker instance.
• Connection Specific: This type of permission is applied at the connection level. A user with this type of permission will see content on pages in the Admin panel that uses a connection associated with a model to which they have data access, even if that connection is used with another model to which they do not have data access.
• Instance Wide: This type of permission applies to the Looker instance as a whole and has three types:
  • nn = No content, No menu: These permissions allow users to perform certain functions across the entire Looker instance, but do not allow users to access content based on models not included in their role’s model set.
  • cn = Content, No menu: These permissions allow users to access content and query information across the entire Looker instance — even for content and queries based on models not included in their role’s model set.
  • cm = Content, Menu: These permissions may expose parts of the Admin menu to non-admin users and and allow users to see information about content and queries based on models not included in their role’s model set.

The following list describes all of the permissions that are available in Looker, in the order in which they appear on the New Permission Set page in the Admin section:

Permissions and Looker Licenses

Looker licenses classify users into three types:

• Developer (Admin)
• Standard (Creator)
• Viewer

The permissions granted to a user determine how that user is classified under the Looker license:

• A user granted the access_data permission but not granted one of the explore, save_content, or develop permissions, is classified as a Viewer user under the Looker license.
• A user granted either of the explore or save_content permissions, but not the develop permission, is classified as a Standard (Creator) user under the Looker license.
• A user granted either the develop permission or the Admin role is classified as a Developer (Admin) user under the Looker license.

Model Sets

A model set defines what data and LookML fields a user or group can see. Each set is a list of LookML models to which a user or group should have access. You can think of a model set as performing two functions:

1. A model set controls which models in your LookML the permissions apply to (if those permissions are model specific).
2. A model set limits what data and LookML fields a user can see, because each model is connected to a specific database connection and contains certain LookML fields.

Creating a Model Set

To create a model set:

1. Click the New Model Set button at the top of the Roles page.

2. Looker displays the New Model Set page. Enter a name for the new model set.

3. Select the model or models that should be included in the new model set.

4. Click the New Model Set button at the bottom of the page.

Starting in Looker 6.24, models that are included in pending projects appear in the Models list on the New Model Set and Edit Model Set pages.

Deleting or renaming a model will not change any model sets that include that model. When a model is removed or renamed, we recommend that Looker admins also remove that model’s name from any associated model sets, using the Edit Model Set page. Removing a deleted model’s name from a model set prevents a new model with the same name from unintentionally being included in that model set.

To learn more about models, see the Model Parameters documentation page.

Creating Multiple Models and Model Sets

As an example of using multiple model sets to limit access to data, imagine you have two teams, Marketing and Support. These two teams should not have access to the entire model. You can create two different models, thelook_marketing and thelook_support, that include only the views and fields that are appropriate for their respective teams:

Then, create a model set for each team and grant access to the appropriate model:

Next, create a new role for that group of users and limit their model set to one you just created:

Editing a Model Set

After a model set has been created, to edit it:

1. On the Roles page, click the Edit button to the right of the model set you want to edit.

2. Looker displays the Edit Model Set page. If desired, enter a new name for the model set.

3. Add or remove any models from the model set.

4. Click the Update Model Set button at the bottom of the page.

Starting in Looker 6.24, models that are included in pending projects appear in the Models list on the New Model Set and Edit Model Set pages.

Deleting or renaming a model will not change any model sets that include that model. When a model is removed or renamed, we recommend that Looker admins also remove that model’s name from any associated model sets, using the Edit Model Set page. Removing a deleted model’s name from a model set prevents a new model with the same name from unintentionally being included in that model set.

Deleting a Model Set

To delete a model set, on the Roles page, click Delete to the right of the model set you want to delete: