1. E-library / Digital Repository
  2. Roles and permissions
Reference

Who can do what in E-library / Digital Repository

Separate content preparation, independent decisions, project configuration and analysis.

Who can do what

Permissions by role
RoleContent intakeRequirements and evidenceIndependent reviewTasks and correctionsDelivery and executionProjects and provenance
Digital Repository AdministratorEditViewViewViewViewEdit
Digital Repository OperatorEditEditEditEditEditView
Digital Repository ReviewerViewViewEditViewViewView
Repository Read Only AnalystViewViewViewViewViewView
AdminEditEditEditEditViewEdit

Each role in detail

Digital Repository Administrator

Maintains approved configuration: record entry on Projects, read-only on all operational, review and provenance tables, and access to all four repository pages. No schema editing, deletion, bulk operations or export grants.

Can

  • Manage Projects
  • View application requirements, content files, content items, execution attempts, operation runs, operation steps, Organizations, People, production tasks, review decisions, source mappings, state history

Starts on: Runs requiring reconciliation

Digital Repository Operator

Prepares assigned work: record entry on Content Items, Application Requirements, Production Tasks and Content Files, read-only on configuration, review and provenance tables. Scope to authorized organizations is enforced by workflow guards.

Can

  • Manage application requirements, content files, content items, production tasks
  • View execution attempts, operation runs, operation steps, Organizations, People, Projects, review decisions, source mappings, state history

Starts on: Content intake board

Digital Repository Reviewer

Reviews independent assigned work: record entry on Review Decisions only, read-only on every other table. Reviewers cannot approve their own preparation; the workflow guards enforce reviewer independence.

Can

  • Manage review decisions
  • View application requirements, content files, content items, execution attempts, operation runs, operation steps, Organizations, People, production tasks, Projects, source mappings, state history

Starts on: Submitted revisions

Repository Read Only Analyst

Reads authorized summaries and aggregates across every table plus the four repository pages. No record creation or editing, no schema or administrative capability.

Can

  • View application requirements, content files, content items, execution attempts, operation runs, operation steps, Organizations, People, production tasks, Projects, review decisions, source mappings, state history

Starts on: Delivered content

Admin

Owns user access and initial repository setup under a separately reviewed grant.

Can

  • Manage Users, Organizations, People
  • View Projects, content items, application requirements, content files, production tasks, review decisions, execution attempts, operation runs, operation steps, source mappings, state history

Set up E-library / Digital Repository your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started