Skip to main content
Platinur stores product-owned portal metadata in a local SQLite database for the single-host v1 footprint.

​
Stored metadata

  • Portal users.
  • Password hashes.
  • Login sessions.
  • Role assignments.
  • Audit events.
  • Assistant messages.
  • Proposed changes and proposal file diffs.
  • Proposal validation, approval, rejection, PR, and promotion metadata.
  • Run/action history.
  • Compact state references for source discovery, dbt, Evidence, GitHub, and runtime checks.

​
Roles

  • admin: full portal administration.
  • approver: approve, reject, validate, and promote changes.
  • developer: ask the Assistant to create proposals and run validation.
  • operator: run refreshes, rebuilds, checks, and safe retries.
  • viewer: read-only portal access and assistant explanations.

​
Permission model

Risky actions are protected at the route level. Configuration changes, user administration, runtime runs, proposal validation, PR creation, and audit visibility each require the corresponding portal permission.