RBAC through Lines of Business

Magellan supports role‑based access control (RBAC) organized around lines of business (LoB), giving enterprises a natural way to align data governance with organizational structure.

A top‑level access group is assigned to each line of business, and all schemas, mappings, and rules nested within that LoB automatically inherit its permissions and policies.

Magellan ships seven roles designed for HIPAA §164.308(a)(2)/§164.312(b) and 21 CFR Part 11 §11.10(e)/(j) and §11.200 separation of duties — Reader, Contributor, Approver, Auditor, Compliance Officer, Security Officer, and Administrator. No single role can both edit mappings and read the full audit ledger, and Administrator is intentionally narrowed so it cannot grant the audit roles.

Releases require Contributor + Approver (two-component electronic signature per §11.200), and quarterly ledger attestation is performed by the Compliance Officer — making four-eyes governance enforceable, not optional.

Every grant and revoke writes `RoleGranted` or `RoleRevoked`. Every action against the system carries the actor's role at time of action, embedded in the entry. Last quarter's ledger still shows the role the actor held last quarter, not the role they hold now.

Cross‑LoB collaboration is supported through shared access groups, allowing controlled visibility into assets owned by other business lines without breaking isolation boundaries.

See the post [Why Three Roles Aren't Enough](/blog/rbac-for-hipaa-part-11-audit-ledgers) for the full role-by-role breakdown and regulatory mapping.