[docs] Document RBAC role: concept, flows, and reference update - #67
Draft
github-actions[bot] wants to merge 1 commit into
Draft
[docs] Document RBAC role: concept, flows, and reference update#67github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Deploying coredocs with
|
| Latest commit: |
9c69f3e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://29bbd5f9.coredocs.pages.dev |
| Branch Preview URL: | https://docs-access-governance-role.coredocs.pages.dev |
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
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.
Ezhuthachan
Documents the RBAC role primitive for
access-governance/role, as requested in #62.<doc-types>was omitted, so all three layers are covered.Added
concepts/access-governance/role.mdx— plain-language concept: what a role holds, contexts, system vs custom roles, how a role reaches a user.flows/access-governance/create-a-role.mdx— create a custom role from the admin RBAC page.flows/access-governance/edit-a-role.mdx— edit a custom role, and clone any role (including a system role).flows/access-governance/_category_.json— new flow domain folder.Both flows are listed in the manual flow sidebar for each version.
Changed (rewritten sections, not whole files)
references/access-governance/role.mdx— added a## Viewsetsection (authorization is superuser-only for writes, filters, permission replacement on update, delete guard) and a## Permission and role syncsection forsync_permissions_roles. Corrected the claim that a user with "the right permission" can delete a custom role: the viewset requiresis_superuser. Added concept and flow links.concepts/access-governance/access-control.mdx— added links to the new concept and flow. No other line changed.All files are mirrored byte-identical to
version-3.0andversion-3.1, along with both sidebar files.Traced to
care/security/models/role.py,care/security/models/permission.pycare/security/api/viewsets/roles.py,care/security/utils/permission_class.pycare/emr/resources/role/spec.pycare/security/roles/role.py,care/security/permissions/base.py,care/security/permissions/constants.pycare/security/management/commands/sync_permissions_roles.pycare_fe:src/Routers/routes/adminRoutes.tsx,src/components/ui/sidebar/admin-nav.tsx,src/pages/Admin/Roles/RolesIndex.tsx,src/pages/Admin/Roles/RoleForm.tsx,src/types/emr/role/role.ts,public/locale/en.jsonLeft out
## Permissionstables state the account type, not a permission name. The role viewset has no permission slug:permissions_controllerreturnsTruefor read andrequest.user.is_superuserfor every write.src/config/keyboardShortcuts.jsondefines none for the roles page.Validation
npm run build—[SUCCESS]forenandml, exit code 0. Corruption scan clean.