Merge pull request #761 from MBishop17/default-custom-role

Default custom role
This commit is contained in:
Denise
2018-09-06 17:00:30 -07:00
committed by GitHub
@@ -22,15 +22,31 @@ While Rancher comes out-of-the-box with a set of default user roles, you can als
1. From the **Global** view, select **Security > Roles** from the main menu.
2. Click **Add Role**.
1. **v2.0.7 and later only:** Select a tab to determine the scope of the roles you're adding. The tabs are:
3. **Name** the role.
- **Cluster**
4. Choose whether to set the role to a status of [locked]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/locked-roles/).
The role is valid for assignment when adding/managing members to _only_ clusters.
- **Project**
The role is valid for assignment when adding/managing members to _only_ projects.
>**Note:** You cannot edit the Global tab.
1. Click **Add Cluster/Project Role**.
1. **Name** the role.
1. Choose whether to set the role to a status of [locked]({{< baseurl >}}/rancher/v2.x/en/admin-settings/rbac/locked-roles/).
Locked roles cannot be assigned to users.
5. Assign the role a **Context**. Context determines the scope of role assigned to the user. The contexts are:
1. **v2.0.7 and later only:** Choose a **Cluster/Project Creator Default** option setting. Use this option to set if the role is assigned to a user when they create a new cluster or project. Using this feature, you can expand or restrict the default roles for cluster/project creators.
>**Note:** Out of the box, the Cluster Creator Default and the Project Creator Default roles are `Cluster Owner` and `Project Owner` respectively.
1. **v2.0.6 and earlier only:** Assign the role a **Context**. Context determines the scope of role assigned to the user. The contexts are:
- **All**