Add docs for user roles #3099
Merged
Add docs for user roles #3099
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
evankanderson
previously approved these changes
Apr 15, 2024
| When incorporating a user into your project, it's crucial to assign them the appropriate role based on their responsibilities and required access levels. | ||
| Minder currently offers the following roles: | ||
|
|
||
| - `viewer`: Provides read-only access to the project. Users with this role can view associated resources such as enrolled repositories, rule types, and profiles. |
There was a problem hiding this comment.
I think they can also see the status of rule evaluations, right?
| Minder currently offers the following roles: | ||
|
|
||
| - `viewer`: Provides read-only access to the project. Users with this role can view associated resources such as enrolled repositories, rule types, and profiles. | ||
| - `editor`: Grants the same permissions as the viewer role, along with the ability to edit project resources, excluding the project itself and the list of providers. |
There was a problem hiding this comment.
How about "in addition to the viewer permissions, editors can author profiles and rule types, as well as add resources to manage. Editors cannot enroll additional providers or change or delete projects."
|
|
||
| - `viewer`: Provides read-only access to the project. Users with this role can view associated resources such as enrolled repositories, rule types, and profiles. | ||
| - `editor`: Grants the same permissions as the viewer role, along with the ability to edit project resources, excluding the project itself and the list of providers. | ||
| - `admin`: Grants administrator rights on the project. Users with this role have the same permissions as editor and can also modify the project and associated providers. |
There was a problem hiding this comment.
Do you want to say "full permissions" here? Maybe also mention that administrators can add and remove users from other roles?
| - `viewer`: Provides read-only access to the project. Users with this role can view associated resources such as enrolled repositories, rule types, and profiles. | ||
| - `editor`: Grants the same permissions as the viewer role, along with the ability to edit project resources, excluding the project itself and the list of providers. | ||
| - `admin`: Grants administrator rights on the project. Users with this role have the same permissions as editor and can also modify the project and associated providers. | ||
| - `policy_writer`: Allows users to create rule types and profiles. |
There was a problem hiding this comment.
Is this also granted by editor? Might be worth contrasting the two.
eleftherias
force-pushed
the
docs-user-roles
branch
from
c50c89d
to
1631790
Compare
eleftherias
force-pushed
the
docs-user-roles
branch
from
1631790
to
d6e5dbe
Compare
dmjb
approved these changes
Apr 15, 2024
ethomson
approved these changes
Apr 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Change Type
Mark the type of change your PR introduces:
Testing
Outline how the changes were tested, including steps to reproduce and any relevant configurations.
Attach screenshots if helpful.
Review Checklist: