Responsibility and assignments

Responsibility describes who is accountable for a specific record or piece of work. Assignments attach that responsibility to the record so users can see who owns the next step, who is reviewing, or which team is handling the item.

Assignments are not the same as roles. A role can give broad permission across a record type, while an assignment explains why a person or team is connected to one concrete record.

Each responsibility has a stable key and an active definition that specifies whether it accepts users, Responsibility Groups, or both; how many subjects are allowed; and whether it is required while the record is active. Assignment Rules independently authorize Add, Replace, and Close operations and validate eligible targets.

Changes are atomic and auditable. Exact no-op requests do not create a new history entry, while successful changes record normalized before/after snapshots. History can remain readable after a responsibility definition is disabled when the current Entity Security configuration grants View and Responsibilities:History.

Assignments may participate in Security Statements, but they do not automatically grant access. Permission Assignments still decide View, actions, and fields for every request.