Keep preparation, review, configuration and reading responsibilities clear.
The operator enters cases, requirement lines, actions and documents for authorized organizations.
The reviewer records decisions and reads the evidence behind a submitted case.
The administrator maintains service definitions; Admin handles user access.
The analyst can inspect authorized records and summaries without changing case work.
| Role | Service configuration | Case intake | Requirements and documents | Independent review | Delivery and actions | Execution provenance |
|---|---|---|---|---|---|---|
| Read Only Analyst | View | View | View | View | View | View |
| Land Revenue Administrator | Edit | Edit | View | View | View | View |
| Land Revenue Operator | View | Edit | Edit | Edit | Edit | View |
| Land Revenue Reviewer | View | View | View | Edit | View | View |
| Admin | View | View | View | View | — | View |
Reads authorized summaries and aggregates across every table plus the four portal pages. No record creation or editing, no schema or administrative capability.
Starts on: Delivered cases
Maintains approved configuration: record entry on Public Services, read-only on all operational, review and provenance tables, and access to all four app pages. No schema editing, deletion, bulk operations or export grants.
Starts on: Case workboard
Prepares assigned work: record entry on Cases, Case Requirements, Case Actions and Case Documents, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.
Starts on: Open assigned actions
Reviews independent assigned work: record entry on Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.
Starts on: Open assigned actions
Maintains user access and coordinates configuration with the responsible service owner.
Start free, then use Proto to change fields, steps and approvals before your team goes live.