A responsibility Role is a node within an Axis. It represents what people own or belong to. A holder is a person assigned to that Role. Neither concept is the same as an access role.
Responsibility Role
Organizational accountability.
- Belongs to an Axis
- Can form a parent-child tree
- Carries holders
- Used for Standard ownership and visibility
Access role
Product authorization.
- Grants permissions such as read or write
- Managed in Administration
- A person may have several grants
- Does not say what the person owns
Holders make accountability human
A Role can describe a stable responsibility while people change. Assigning a holder connects that durable node to the person accountable now.
Several holders
Where the product allows several holders, the Role may represent shared responsibility. Do not use extra holders merely to grant access; access belongs in the access-role model.
Role trees and visibility
A person reads Role-scoped content only when they hold one of the Roles it names. The relationship is exact: there is no inheritance up or down the Role tree. This relationship should mirror real organizational responsibility rather than an improvised security group.
Naming Roles
Use the organization’s established responsibility names. Accountability follows the Role rather than the person, so a holder can change without the material losing its owner.