Off-board On-Call Team and User guide #31979
Open
+81
−0
Conversation
This file contains hidden or 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
Preview links (active after the
|
|
Hi there, I am adding the |
Dalje-et
changed the title
|
Done @iadjivon :) |
git-thuerk-done
requested changes
Oct 7, 2025
There was a problem hiding this comment.
Hi @Dalje-et looks good, I have a few suggestions and then the links need defined within the page, let me know when this is ready for re-review!
|
|
||
| ### Remove user notification preferences | ||
|
|
||
| If the user is still part of your organisation you can ask them to remove their Notification Preferences in their On-Call profile by visiting On-Call > Settings > My On-Call Profile. |
There was a problem hiding this comment.
Suggested change
| If the user is still part of your organisation you can ask them to remove their Notification Preferences in their On-Call profile by visiting On-Call > Settings > My On-Call Profile. | |
| If the user is still part of your organization you can ask them to remove their Notification Preferences in their On-Call profile by visiting **On-Call > Settings > My On-Call Profile**. |
|
|
||
| As an admin, you can also take care of it yourself by visiting On-Call > Settings > Notification Preferences. Find the right user and remove their notification preferences whenver needed. You will need the "On-Call Admin" permission to perform this. | ||
|
|
||
| **Note**, Notification Preferences make a user pageable and therefore billable. Having only contact methods (e.g. push notifications) defined is a non-billable action and won't incur charges. |
There was a problem hiding this comment.
Suggested change
| **Note**, Notification Preferences make a user pageable and therefore billable. Having only contact methods (e.g. push notifications) defined is a non-billable action and won't incur charges. | |
| **Note**, Notification Preferences make a user pageable and therefore billable. Having only contact methods (for example, push notifications) defined is a non-billable action and won't incur charges. |
|
|
||
| If the user is still part of your organisation you can ask them to remove their Notification Preferences in their On-Call profile by visiting On-Call > Settings > My On-Call Profile. | ||
|
|
||
| As an admin, you can also take care of it yourself by visiting On-Call > Settings > Notification Preferences. Find the right user and remove their notification preferences whenver needed. You will need the "On-Call Admin" permission to perform this. |
There was a problem hiding this comment.
Suggested change
| As an admin, you can also take care of it yourself by visiting On-Call > Settings > Notification Preferences. Find the right user and remove their notification preferences whenver needed. You will need the "On-Call Admin" permission to perform this. | |
| As an admin, you can also manage this yourself by navigating to **On-Call > Settings > Notification Preferences**. Find the appropriate user and remove their notification preferences as needed. You will need the "On-Call Admin" permission to perform this. |
| ## Further reading | ||
|
|
||
| {{< partial name="whats-next/whats-next.html" >}} | ||
|
|
There was a problem hiding this comment.
I noticed you have links here to on-call pages and rbac but don't see them defined within the page, can you add them in where needed ? thanks!
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?
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes