Skip to content

Administration

Admins configure the studio from Settings (the gear icon in the top bar). Because fxquinox is metadata-driven, most configuration is editing data — every change is picked up by the web UI, the SDK, and the API immediately, with no redeploy.

Settings is divided into five groups accessible from the sidebar:

  • Objects and schemas

    Entity types, their fields, and the workflow schemas that scope what each project uses.

  • Statuses, steps and priorities

    The status codes, state mappings, legal transitions, pipeline steps, and priorities that drive workflow across every view.

  • Users and access

    People, roles, and programmatic access via API keys.

  • Branding

    Company name, logo, favicon, and accent colour.

  • Security

    Authentication model, authorization rules, and the pre-1.0 security review findings.

Settings sidebar groups

Group Sections
General Custom Branding, Notifications
Workflow Schemas, Statuses, Transitions, Steps, Priorities, Objects
Project Asset Types, Product Types
Resources Users & Groups
Automation Webhooks, Automations, Scheduled, Addons

How it maps to the model

Settings configure the schema layer: entity types, fields, statuses, steps, and priorities are all records stored in the same database as shots and tasks. The actual production data is shaped by those records. See How it works for the full model.

Before opening fxquinox to a team

Change the default demo@fxquinox.dev admin password and follow the production hardening checklist. Open registration (POST /auth/register) is public by design for bootstrap; gate it at the reverse proxy for locked-down installs.