DOCCS-2807: Publish Calico Cloud February 2026 #2500
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
This PR publishes the Calico Cloud February 2026 release documentation, introducing a new feature for namespaced access to dashboards. The changes allow administrators to restrict user dashboard access to specific namespaces using custom role permissions.
Changes:
- Added February 3, 2026 release notes documenting the namespaced dashboard access feature
- Updated custom roles documentation to explain namespace-scoped dashboard permissions
- Enhanced dashboards documentation with detailed role access information
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| calico-cloud_versioned_docs/version-22-2/release-notes/index.mdx | Adds February 2026 release notes with namespaced dashboards feature and important note about permission changes |
| calico-cloud_versioned_docs/version-22-2/users/create-and-assign-custom-roles.mdx | Documents new dashboard permission behavior for namespaced access |
| calico-cloud_versioned_docs/version-22-2/observability/dashboards.mdx | Adds role access section clarifying which roles have dashboard access and namespacing capabilities |
| calico-cloud/users/create-and-assign-custom-roles.mdx | Same updates as versioned file for current development version |
| calico-cloud/observability/dashboards.mdx | Same updates as versioned file for current development version |
| #### Feature 1 | ||
|
|
There was a problem hiding this comment.
The placeholder "Feature 1" should be removed or replaced with actual content before publishing this release. Placeholder content should not be included in production documentation.
| #### Feature 1 |
| #### Feature 3 | ||
|
|
There was a problem hiding this comment.
The placeholder "Feature 3" should be removed or replaced with actual content before publishing this release. Placeholder content should not be included in production documentation.
| #### Feature 3 |
| ### Bug fixes | ||
|
|
||
| * TBD | ||
|
|
There was a problem hiding this comment.
The placeholder "TBD" in the bug fixes section should be replaced with actual bug fix information or the entire bug fixes section should be removed if there are no bug fixes to document. Publishing "TBD" in production documentation is not appropriate.
| ### Bug fixes | |
| * TBD |
| Not all users have access to dashboards. | ||
| Creating custom dashboards is limited to administrators. | ||
| Administrators can limit a user's access to dashboards for a particular cluster or for particular namespaces in a cluster. |
There was a problem hiding this comment.
The statements "Not all users have access to dashboards" and "Administrators can limit a user's access to dashboards" contradict the preceding list which states that Viewer role has access to all dashboard information. This creates confusion about which users actually have dashboard access. Consider clarifying that while these standard roles have full access, custom roles may have restricted access, and rewording to avoid the contradiction.
| Users with custom roles can access dashboards if they have sufficient permissions. | ||
|
|
||
| Not all users have access to dashboards. | ||
| Administrators can limit a user's access to dashboards for a particular cluster or for particular namespaces in a cluster. |
There was a problem hiding this comment.
The statements "Not all users have access to dashboards" and "Administrators can limit a user's access to dashboards" contradict the preceding list which states that Viewer role has access to all dashboard information. This creates confusion about which users actually have dashboard access. Consider clarifying that while these standard roles have full access, custom roles may have restricted access, and rewording to avoid the contradiction.
| Users with custom roles can access dashboards if they have sufficient permissions. | |
| Not all users have access to dashboards. | |
| Administrators can limit a user's access to dashboards for a particular cluster or for particular namespaces in a cluster. | |
| Users with custom roles can access dashboards if their role includes dashboard permissions. | |
| Users must be assigned one of the standard roles above, or a custom role with dashboard permissions, to access dashboards. | |
| Administrators can limit dashboard access for custom roles, for example to specific clusters or namespaces in a cluster. |
ctauchen
changed the title
Product Version(s):
Issue:
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: