Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-11-10 01:19:53 +01:00
Code Issues Projects Releases Wiki Activity

docs: update private project collaboration mode explanation (#10892)

Browse Source
This commit is contained in:
Melinda Fekete 2025-10-30 17:03:16 +01:00 committed by GitHub
parent d089e771da
commit a14c5c7f57
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/reference/project-collaboration-mode.md
View File

@ -32,14 +32,16 @@ All users of your Unleash instance can view the project but only project Members
### Private collaboration mode ### Private collaboration mode
Only project Members, Admins, Editors, and users with [custom root roles](./rbac#custom-root-roles) can view the project. Viewers, who are not project Members, can't see the project in the project list. Only project Members and Admins can submit change requests. Only project Members, Admins, Editors, and users with any [custom root role](./rbac#custom-root-roles) can view the project. Viewers, who are not project Members, can't see the project in the project list. Only project Members and Admins can submit change requests.
To grant users visibility into private projects through a custom root role, you must assign the role directly to the user rather than through a [user group](/reference/rbac#usergroups).
| | View project | Submit change requests | | | View project | Submit change requests |
|-----------|-------------------------------------------------------------------------------------------------|----------------------------| |-----------|-------------------------------------------------------------------------------------------------|----------------------------|
| Open | All users | All users | | Open | All users | All users |
| Protected | All users | Project Members and Admins | | Protected | All users | Project Members and Admins |
| Private | Project Members, Admins, Editors, and users with [custom root roles](rbac.md#custom-root-roles) | Project Members and Admins | | Private | Project Members, Admins, Editors, and users with any [custom root role](rbac.md#custom-root-roles) assigned directly (not through a user group) | Project Members and Admins |
## Set project collaboration mode ## Set project collaboration mode

2
website/docs/reference/rbac.md
View File

@ -326,6 +326,8 @@ Groups themselves do not grant permissions. To be functional, a group must eithe
A user can belong to multiple groups, and each group a user belongs to can have a different role assigned to it on a specific project. A user can belong to multiple groups, and each group a user belongs to can have a different role assigned to it on a specific project.
If a user gains permissions for a project through multiple groups, they will inherit the most permissive set of permissions from all their assigned group roles for that project. If a user gains permissions for a project through multiple groups, they will inherit the most permissive set of permissions from all their assigned group roles for that project.
You can’t add a group with a [custom root role](#custom-root-roles) to a project. If you need both root-level and project-level access through [group syncing](#set-up-group-sso-syncing), you can sync the same directory group from your Active Directory or identity provider to two separate Unleash groups: one for root permissions and one for project access.
## Set up group SSO syncing ## Set up group SSO syncing
:::note Availability :::note Availability