Trust & Admin Overview

What WyrdOS documents today for access, API keys, audit posture, data controls, and enterprise handoff

Trust in WyrdOS comes from visible structure: who can access a workspace, how automation authenticates, what changed, and how work links back to strategy.

Status At A Glance

Area	Documented status
Workspaces	WyrdOS supports personal and organisation-level workspaces.
API keys	Keys are workspace-scoped and can carry read, write, and delete permissions.
Resource visibility	API responses are scoped to the authenticated key and workspace visibility.
Evidence workflow	Agents can propose candidate evidence; WyrdOS users approve or reject it.
Audit trail	Evidence proposal approval/rejection preserves review history. Full admin audit requirements should be confirmed for each deployment.
SSO and compliance	Enterprise requirements are handled through support until deployment-specific docs are agreed.
Data import/export	API and CLI surfaces support structured reads and writes. Enterprise migrations should be planned with support.

Admin Docs

Quality Bar

Do not treat a workspace as production-ready until:

Admins know which users belong to the workspace.
API keys are scoped to the least permission needed.
External agents create evidence proposals instead of silently writing accepted evidence.
Deletion, export, and migration paths are understood for the deployment.
Unsupported compliance claims are not made in sales or onboarding material.