--output table|json. JSON mode never prompts or emits progress banners. Destructive JSON commands require --force or --yes.
Core administration requires the admin role. Review commands are also available to global reviewers and authorized teamspace owners or reviewers. Some role changes require super_admin.
Commands
Settings
settings returns the direct settings array. Sensitive values are redacted by the server. set returns the server setting object and never echoes the supplied value in human output.
A positional setting value may be retained by shell history. Prefer deployment secret files for sensitive settings that support external management.
Users and roles
List users:super_admin, admin, reviewer, and user.
Create with a chosen password only when shell-history exposure is acceptable:
--generate. Created and generated passwords are returned once. Treat the entire result as a secret and do not paste it into logs, issues, or chat.
Change a role:
--force or --yes is present. JSON deletion requires confirmation through one of those flags.
Diagnostics and policy
diagnostics returns the direct health object. Trace privacy responses return trace_privacy. Cache clear returns the number of cleared entries.
SAML
Show redacted configuration:--idp-slo-url, --sp-entity-id, --jit|--no-jit, and --active|--inactive. Certificate and private-key material is never returned by configuration reads.
Delete configuration:
--force or --yes.
SCIM tokens
Security events
info, warning, or critical. Limit accepts 1 through 1,000 and offset accepts zero or greater. JSON returns the server envelope with events and total.
Audit log
Query events:server or cli. Limit accepts 1 through 500.
Print CSV to stdout:
--force or --yes is provided. Audit exports can contain sensitive administrative data.
Review queue
Reviews are revision-based and use theobserval review command group. Content is visible only to participants and authorized reviewers.
observal review --help for threads, comments, reviewer requests, dismissal, and watch/mute.
Automated checks (experimental)
Experimental and off by default. A super admin or admin turns it on under Settings, Experimental (experimental.review_checks). While off, the checks tab, queue labels, settings and endpoints below are hidden, and automated checks neither run nor block publishing; the built-in secret, schema and skill folder checks still apply.
Each revision runs built-in checks (secret scan, required fields, skill folder validity) plus configurable automated checks on the worker, within about 15 seconds of submission:
Checks that contact external hosts, other than the Git source check, are off by default. Every check is advisory by default; an admin or team owner can mark one as blocking. A blocking check that is queued, running, failed or errored holds publication, including automatic publication. A check that could not run reports
skipped or error, never pass.
Settings are scoped. Admins edit the organization settings (used for public items) with the gear button on the review queue, or PUT /api/v1/admin/review-checks. Team owners and admins edit their teamspace’s settings (used for team-visible items) on the teamspace Settings tab, or PUT /api/v1/teams/{id}/review-checks. Changes apply to new revisions; POST /api/v1/reviews/{number}/checks/rerun re-queues an open review under the current settings. These checks are static and network lookups: they do not prove a component is safe or that it works.
Exit codes
Related
observal auth: inspect the active account and roleobserval inbox: review and security notificationsobserval ops: sessions, telemetry, logs, and insights

