DOCS-12791 Add governance console overview page #33335
Conversation
github-actions
bot
added
Architecture
Preview links (active after the
|
| Governance Console unifies the configuration and administration of a large, multi-team, multi-organization Datadog account. For organizations who need centralized governance, strong defaults, and automatic policy enforcement, Governance Console helps establish and maintain a best practice, compliant environment. | ||
|
|
||
| Governance Console helps teams understand how their organization is adopting and using Datadog. It provides a centralized, self-service view of Datadog usage and adoption. Governance Console offers control and predictability over the platform's configuration, usage, and cost, helping administrators holistically manage their Datadog deployment. Datadog turns your organization's configuration and usage activity into metrics and insights to guide optimization and investment. | ||
|
|
||
| Governance Console supports both new and existing customers, helping new customers start from a well-managed setup, and helping existing customers mature and adopt best practices over time. |
There was a problem hiding this comment.
I think this overview section is much too long, a bit repetitive, does too much selling/persuading, and too vague / isn't sufficiently concrete. I think the opening sentence really needs to describe what Governance Console literally is (a page/section in Datadog that displays particular information). We can then offer some brief justification for why you'd want to use it and what specific use-cases it would be most helpful for. I'm also really struggling with the last sentence about how it supports both new and existing customers.... shouldn't all products support new and existing customers?
|
|
||
| Governance Console supports both new and existing customers, helping new customers start from a well-managed setup, and helping existing customers mature and adopt best practices over time. | ||
|
|
||
| {{< img src="account_management/governance_console/governance-console-overview.png" alt="Governance console screenshot, showing summary" style="width:100%;" >}} |
There was a problem hiding this comment.
i'd love to see more detailed alt text. I think just having a few examples of the types of metrics shown on this page (active dashboards, active integrations, etc.) would really really enhance someone's understanding of what this feature is and what it provides.
|
|
||
| {{< img src="account_management/governance_console/log-management-product.png" alt="Governance console screenshot, showing Log Management metrics" style="width:100%;" >}} | ||
|
|
||
| ## Establish guardrails |
There was a problem hiding this comment.
Is there a more concrete way we can phrase this? I find this heading to be a little vague.
Also, if this is about the Controls tab, let's put the word "Controls" in the heading to make this all easier to scan. So something like "Use controls to enforce organization policies"
|
|
||
| ## Establish guardrails | ||
|
|
||
| Datadog governance controls help you automatically implement policies in your Datadog organization by identifying configuration drift, notifying the accountable users, and enforcing compliance. Each control helps establish and maintain a best practice, compliant environment. |
There was a problem hiding this comment.
| Datadog governance controls help you automatically implement policies in your Datadog organization by identifying configuration drift, notifying the accountable users, and enforcing compliance. Each control helps establish and maintain a best practice, compliant environment. | |
| Datadog governance controls help you automatically implement policies in your Datadog organization by identifying configuration drift, notifying the accountable users, and enforcing compliance. Each control helps establish and maintain compliance with best practices. |
trying to massage the grammar here— "a best practice, compliant environment" doesn't parse as correct to me, but my suggestion probably isn't ideal either
| ### Access control | ||
|
|
||
| The `governance_console_read` permission controls access to the Governance Console. Users with `governance_console_read` assigned to their role have access to view the Governance Console UI and associated reporting and insights. | ||
|
|
||
| Product-specific permissions restrict users' ability to change product-specific settings. For example, modifying or automating metrics configuration requires the `metrics_write` permission. |
There was a problem hiding this comment.
It's a bit weird to me that this section is under the "Establish guardrails" h2 section — it looks like users need this permission to see the Governance Console at all, including anything described in the "Explore usage insights" h2 section.
- I think I'd move this section up into "Explore usage insights"
- I don't love the heading "Access control" - my first assumption was that this section would be about how you can use Governance Console to perform access control actions for your org, not what permissions you need to use Governance Console. Maybe change this heading to "Required permissions for Governance Console" or something similar
mlorenz92
left a comment
mlorenz92
left a comment
There was a problem hiding this comment.
Approved, assuming Cecilia's comments are addressed
urseberry
force-pushed
the
uchen/governance
branch
from
bc32ec4 to
2ebb637
Compare
3 participants
What does this PR do? What is the motivation?
Adds the overview page documenting the new Governance Console.
Removes a duplicate entry in the main menu file.
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