Doc on Roles and Governance / Roles & Permissions

[john-d03]

/document Access & Governance/Roles & Permissions

[github-actions]

✅ Ezhuthachan completed successfully!

[github-actions]

Ezhuthachan

I opened a pull request for /document Access & Governance/Roles & Permissions.

What I wrote (in version-3.0, mirrored to version-3.1):

• Rewrote the concept concepts/access-governance/access-control.mdx ("Roles & Permissions") to the current concept template. The old page predated it and exposed permission slugs and raw context values in user-facing text.
• Added two flows: flows/access-governance/create-a-role and flows/access-governance/assign-a-role-to-a-user, and listed them in both version sidebar files under a new Access & Governance flow category.
• Left the reference layer alone. references/access-governance/role.mdx, permission.mdx and permission-association.mdx already match care/security/models/ and care/emr/resources/role/spec.py.

The request gave a domain and a topic rather than a domain/slug, so I mapped it to the existing access-governance domain and kept the access-control slug, because the organization and user concepts already link to it.

npm run build is green for en and ml, and the corruption scan returns nothing.

Open questions

1. RoleAssociation in care/security/models/permission_association.py has an expiry field, but I found no screen in care_fe that sets or shows it. Is role expiry a live feature? If it is, the assign flow needs a step for it.
2. Should there be a third flow for department-level roles inside a facility (care_fe/src/pages/Facility/settings/.../EditFacilityUserRoleSheet.tsx)? I read the request as being about roles themselves, so I left it out.

Bugs and inconsistencies

1. The Administration navigation labels are hard-coded English and never translate. In care_fe/src/components/ui/sidebar/admin-nav.tsx, the entries RBAC, Permissions, Roles, Organizations, Governance, Suppliers and Responsibilities are plain string literals in the nav definition, not t(...) calls with keys in public/locale/en.json. Every other sidebar label in the app goes through i18n, so in the Malayalam locale this whole section stays in English. Confidence: high — I checked each of those strings against public/locale/en.json and found no matching key.
2. can_list_organization_users has a malformed display name. In care/security/permissions/organization.py the name is "Can List Users in an Organizations" — "an" with a plural. It is user-visible on the Permissions admin screen. Confidence: high, though it is cosmetic. I did not reproduce the typo in the docs; I wrote the permission in plain words instead.

Generated by Ezhuthachan for #60 · opus50 · 345.5 AIC · ⌖ 19.1 AIC · ⊞ 14.4K · ◷
_{Comment /document to run again}