improved short descriptions for reasoning for adding members to clusters or projects

This commit is contained in:
Mark Bishop
2018-06-18 17:09:48 -07:00
committed by Mark Bishop
parent d4552d5c17
commit b3b5e240d3
2 changed files with 5 additions and 3 deletions
@@ -3,9 +3,9 @@ title: Adding Cluster Members
weight: 3525
---
Before a user can access a cluster and its resources, the cluster owner must explicitly assign that user a cluster _membership_ (or a project membership, which is out of scope for this topic). Assigning a user membership to a cluster provides them with access to and roles within the cluster.
If you want to provide a user with access and permissions to _all_ projects within a cluster, assign the user a cluster membership.
<!-- TODO: add link to project membership after the topic is created-->
>**Tip:** Want to provide a user with access to a _specific_ project within a cluster? See [Adding Project Members]({{< baseurl >}}/rancher/v2.x/en/tasks/projects/add-project-members/) instead.
There are two contexts where you can add cluster members:
@@ -4,7 +4,9 @@ weight:
draft: true
---
Before a user can access a project and its resources, the project owner must explicitly assign that user a project _membership_, which provides the user with access and roles within the project.
If you want to provide a user with access and permissions to _specific_ projects within a cluster, assign the user a project membership.
>**Tip:** Want to provide a user with access to _all_ projects within a cluster? See [Adding Cluster Members]({{< baseurl >}}/rancher/v2.x/en/tasks/clusters/adding-managing-cluster-members) instead.
There are two contexts where you can add project members: