[CASEM-1642] Add Granular Access Control in case Management #27153
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
sysy6r
changed the title
sysy6r
force-pushed
the
sylvain.cizaire/add-granular-project-rbac
branch
from
a8f9ed4 to
7cf7a84
Compare
kayayarai
added
Do Not Merge
urseberry
reviewed
Jan 21, 2025
|
|
||
| By default, access to projects and cases is unrestricted. [Granular Access Control][1] can be used to manage the permissions of users, teams, roles, or your full organization at the project level. There are four sets of permissions that can be used: | ||
| - **Manager**: Users can create and edit cases, views, settings, and permissions of the project, and can delete the project. | ||
| - **Contributor**: Users can create, comment and edit cases, but not change settings or permissions or the project. |
There was a problem hiding this comment.
Suggested change
| - **Contributor**: Users can create, comment and edit cases, but not change settings or permissions or the project. | |
| - **Contributor**: Users can create, comment on, and edit cases. They can't change settings, permissions, or the project. |
| By default, access to projects and cases is unrestricted. [Granular Access Control][1] can be used to manage the permissions of users, teams, roles, or your full organization at the project level. There are four sets of permissions that can be used: | ||
| - **Manager**: Users can create and edit cases, views, settings, and permissions of the project, and can delete the project. | ||
| - **Contributor**: Users can create, comment and edit cases, but not change settings or permissions or the project. | ||
| - **Viewer**: Users can view and watch all cases, views and settings of the project. They can’t create, edit, or comment on cases. |
There was a problem hiding this comment.
Suggested change
| - **Viewer**: Users can view and watch all cases, views and settings of the project. They can’t create, edit, or comment on cases. | |
| - **Viewer**: Users can view and watch all cases, views, and settings of the project. They can’t create, edit, or comment on cases. |
| - **Viewer**: Users can view and watch all cases, views and settings of the project. They can’t create, edit, or comment on cases. | ||
| - **No Access**: Users can’t view any cases, views, or settings of the project. | ||
|
|
||
| Note that other Datadog products that integrate with Case Management in an automated way such as Monitors are able to create cases within a project regardless of the project’s access settings |
There was a problem hiding this comment.
Suggested change
| Note that other Datadog products that integrate with Case Management in an automated way such as Monitors are able to create cases within a project regardless of the project’s access settings | |
| **Note:** Other Datadog products that integrate with Case Management, such as Monitors, are able to automatically create cases within a project regardless of the project’s access settings. |
There was a problem hiding this comment.
This image contains company email addresses. Please blur the address or replace them with fake emails. Alternately, you could remove this image. The doc is clear and understandable without it, and images create a maintenance burden.
urseberry
approved these changes
Jan 30, 2025
|
Sylvain wants this merged Thursday February 6. |
…m:DataDog/documentation into sylvain.cizaire/add-granular-project-rbac
|
cc @urseberry I just re-ordered the list of resources in the table (last commit) as I noticed they are supposed to be in alphabetical order. Also, feel free to merge, everything is ready on our side 🚀 |
|
/merge |
Devflow running:
|
dd-devflow
bot
added
mergequeue-status: queued
mergequeue-status: in_progress
and removed
mergequeue-status: queued
labels
dd-mergequeue
bot
deleted the
sylvain.cizaire/add-granular-project-rbac
branch
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.
What does this PR do? What is the motivation?
Case Management team is going to be releasing Project-level Access Control end of january. We want to update the public documentation to guide users as to what they can expect from this new feature.
Also, we are in the same release removing the Membership concept in case management : users won't be able to be a member of project, or to join or leave a project. so, we want to remove that from the documentation as well
Merge instructions
It's not ready to be merged. We want to merge this after we have GA the feature end of january
Merge readiness: