Roles, scopes, and permissions
Access in ProgramsFlow combines a role with an optional college or department scope, enforced on every read and write — from committee reviews to program edits and public publishing.
Roles plus scopes
Every user has a role — administrator, committee member, faculty, and others — optionally narrowed by a scope: a specific college or department. An admin without a scope manages the whole institution; a department-scoped admin manages only their department's programs, courses, and cases. Scope is enforced on the server for both reading and writing, not just hidden in menus.
Committees and stage responsibility
Workflow stages assign responsibility to committees or roles. Only members of the responsible party at the current stage can submit, review, or advance a case — being an administrator elsewhere does not shortcut a committee's mandate. Case discussions are likewise limited to actual participants.
Who can edit program content
Institutions choose how strictly program content is controlled: scoped admins may edit working versions freely, be limited to draft-status programs only, or be required to route every change through a formal amendment case. Approved snapshots are immutable for everyone, and edits to older versions always require institution-wide authority.
The audit trail
Every significant change — approvals, publishes, permission changes, archives — is recorded in an append-only audit log with who, what, and when. Institution-wide admins can browse it for compliance reviews, and participants see a derived timeline on each case.
