Skip to content

Conversation

@ctauchen
Copy link
Collaborator

@ctauchen ctauchen commented Jan 29, 2026

Docs content and release note for namespaced dashboards feature.

Product Version(s):

Issue:

Link to docs preview:

Release note: https://deploy-preview-2494--tigera.netlify.app/calico-cloud/release-notes/#namespaced-access-to-dashboards
New section: Role access to dashboards https://deploy-preview-2494--tigera.netlify.app/calico-cloud/observability/dashboards#role-access-to-dashboards
Changes to Dashboard feature area notes: https://deploy-preview-2494--tigera.netlify.app/calico-cloud/users/create-and-assign-custom-roles#required-permissions-for-common-calico-cloud-features
SME review:

  • An SME has approved this change.

DOCS review:

  • A member of the docs team has approved this change.

Additional information:

Merge checklist:

  • Deploy preview inspected wherever changes were made
  • Build completed successfully
  • Test have passed

@ctauchen ctauchen requested a review from a team as a code owner January 29, 2026 16:17
Copilot AI review requested due to automatic review settings January 29, 2026 16:17
@netlify
Copy link

netlify bot commented Jan 29, 2026

Deploy Preview succeeded!

Built without sensitive environment variables

Name Link
🔨 Latest commit 4c3fd0c
🔍 Latest deploy log https://app.netlify.com/projects/tigera/deploys/697b88182ee692000870282b
😎 Deploy Preview https://deploy-preview-2494--tigera.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 68 (no change from production)
Accessibility: 98 (no change from production)
Best Practices: 92 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@netlify
Copy link

netlify bot commented Jan 29, 2026

Deploy Preview for calico-docs-preview-next ready!

Name Link
🔨 Latest commit 4c3fd0c
🔍 Latest deploy log https://app.netlify.com/projects/calico-docs-preview-next/deploys/697b8818a5b1c10008de4936
😎 Deploy Preview https://deploy-preview-2494--calico-docs-preview-next.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@ctauchen ctauchen changed the base branch from main to publish/cc-feb January 29, 2026 16:17
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds documentation for the new namespaced dashboard access feature in Calico Cloud version 22-2 (February 2026 release). The feature allows administrators to grant users dashboard access limited to specific namespaces, improving security by ensuring users only view data for areas they are authorized to manage.

Changes:

  • Added release notes for the namespaced dashboard feature with a breaking change warning about View Network Sets permissions
  • Updated custom roles documentation to explain namespaced dashboard access permissions
  • Enhanced dashboard documentation with role-based access control information

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 7 comments.

File Description
calico-cloud_versioned_docs/version-22-2/users/create-and-assign-custom-roles.mdx Added explanation in the overview about namespaced dashboard permissions and updated the Dashboard row in the permissions table to clarify namespaced access behavior
calico-cloud_versioned_docs/version-22-2/release-notes/index.mdx Added stub release notes for February 2026 with namespaced dashboard feature description and breaking change warning
calico-cloud_versioned_docs/version-22-2/observability/dashboards.mdx Added new "Role access to dashboards" section documenting which user roles can access dashboards and clarifying custom role permissions

@@ -11,7 +11,18 @@ title: Release notes

#### Feature 1
Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The release notes contain placeholder text "#### Feature 1" which should be replaced with actual content or removed before release.

Copilot uses AI. Check for mistakes.
Comment on lines 27 to 28
#### Feature 3

Copy link

Copilot AI Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The release notes contain placeholder text "#### Feature 3" which should be replaced with actual content or removed before release.

Suggested change
#### Feature 3

Copilot uses AI. Check for mistakes.
@ctauchen ctauchen force-pushed the docs-2808-namespaced-dashboards branch 2 times, most recently from bc0a77d to 6fa8d54 Compare January 29, 2026 16:31
Namespaced access to dashboards can be managed by adding namespaces to the **View Network Sets** custom role permission.

:::important
Changes in this release will cause users with the **View Network Sets** custom role permission to lose access to all dashboards.
Copy link
Contributor

@jaderhs jaderhs Jan 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About the Changes in this release... paragraph:

The View Network Sets custom role permission is required for custom role users to view dashboard charts data, so it would be users that do not have the View Network Sets custom role permission that will lose access to dashboards data (all these users are still be able to view the dashboards, but dashboard charts will display the "You do not have permission to view this chart data" message for users that do not have the View Network Sets custom role permission).

FYI this is assuming they do not have one of the predefined roles in the Role access to dashboards section assigned to them.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I've modified the text along the lines we talked about.

@ctauchen ctauchen force-pushed the docs-2808-namespaced-dashboards branch from 6fa8d54 to 22eac62 Compare January 29, 2026 17:27
Copy link
Member

@tmjd tmjd left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here are some comments but you may want to go over my comments with @jaderhs

Namespaced access to dashboards can be managed by specifying namespaces in the **View Network Sets** custom role permission.

:::important
Changes in this release may cause some users with the **View Network Sets** custom role permission to lose access to dashboard data.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jaderhs is this accurate? My understanding is for a custom role, if it doesn't have any "View Network Sets" permissions then they won't have access to dashboard data.


:::important
Changes in this release may cause some users with the **View Network Sets** custom role permission to lose access to dashboard data.
To restore access, administrators must edit their custom roles to explicitly add namespaces to the **View Network Sets** permission.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe it is also an option to give a custom role access to "View Network Sets" in all namespaces in a cluster to give access to all dashboard data in a cluster.


Not all users have access to dashboards.
Creating custom dashboards is limited to administrators.
Access may be limited to a particular cluster or namespace.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd suggest that for custom roles, access will be limited only to clusters that have been given explicit access and those permissions may only be for particular namespaces.
The key part I'm trying to point out is that it isn't possible to say a custom role has access to a particular namespace in all clusters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants