Skip to content

Personas

SISS serves five user groups with different trust boundaries and different primary actions. Human review always remains the controlling authority, even where AI assists extraction, checking, or drafting.

Who uses SISS

Persona Primary actions Trust boundary Importance
Principal Submitting Person (PSP) Submit documents, reply to comments, look up submission status External High
CMU Officer Coordinate submissions, configure workflow, user admin, compile info for OSC approval Internal High
ATD / ATL Officer 1 Review submissions in their department, write comments, sign off Internal or external agency Standard
SIRP Officer Review planning / zoning references, visual BIM inspection Internal panel Standard
External Auditor Read user action logs and decisions Read-only, isolated data surface Standard

How personas interact with the system

graph LR
  PSP([PSP])
  CMU([CMU Officer])
  ATD([ATD / ATL Officer])
  SIRP([SIRP Officer])
  AUD([External Auditor])

  SISS{{SISS platform}}
  BQ[(Audit dataset<br/>BigQuery)]

  PSP -->|submit documents<br/>reply to comments<br/>check status| SISS
  CMU -->|coordinate<br/>configure workflow<br/>admin users| SISS
  ATD -->|review<br/>comment<br/>endorse| SISS
  SIRP -->|planning + BIM review| SISS

  SISS -.writes audit events.-> BQ
  AUD -->|read-only| BQ

Permissions, at a glance

Each persona maps to a seed RBAC role (full detail in Security & RBAC):

Persona Role(s)
PSP PSP
CMU Officer CMU.Officer, optionally CMU.Admin
ATD / ATL Officer ATD/ATL.Officer (department-scoped)
SIRP Officer SIRP.Officer
External Auditor Auditor (read-only BQ dataset)
— System.Admin (platform config, no submission data)

Department scoping is enforced at query time via AlloyDB row-level security, so an ATD/ATL officer only sees submissions routed to their department.

  1. The planning CSV labels this group as "Internal/External Technical Agencies"; the architecture spec uses the shorter ATD/ATL term. Both refer to the same role. ↩