qbrix
On this page

ConsoleWorkspace & API keys

Workspace & API keys

Workspace settings live under Settings in the console. This is where you invite teammates, manage their roles, and rotate API keys.

API keys

Every server-side integration with qbrix uses an API key. Keys are scoped to a workspace and start with the optiq_ prefix.

Creating a key

  1. Settings → API keys → Create API key
  2. Give it a recognizable name (e.g. prod-checkout-service).
  3. Copy the generated key immediately — qbrix only shows it once.

API keys inherit the role of the user that created them. Use a viewer key for read-only integrations and a member key for services that need to write feedback or create experiments.

Rotating a key

Pick Rotate key from the key's overflow menu to generate a fresh secret. The old secret stops working immediately, so coordinate the rotation with your deployment.

Revoking a key

Pick Revoke key from the same menu. Revocation takes effect immediately and there is no undo.

Members & invites

The Members tab lists every member, their role, and the date they joined.

Inviting a teammate

  1. Click Invite Member.
  2. Enter the email and choose a role.
  3. The invitee gets an email with a one-time link that expires in 72 hours.

Pending invites show up in the same table with a Pending status. You can revoke them at any time. A workspace can send 25 invites a day, and revoking an invite doesn't give one back.

Roles

RoleWhat they can do
adminEverything: experiments, gates, members, API keys
memberExperiments, pools, gates, agents, insights — but not workspace settings
viewerRead-only across all resources

Roles are enforced server-side by RBAC scopes — the console just hides controls the user can't use. See the API reference for the full scope list.

Billing

The Billing tab appears only on qbrix's managed hosting, where it shows your plan and usage. A self-hosted install has no billing and no usage limits.

Profile

The Profile tab lets each user update their display name, email, and password. Email changes require re-verification.

Next steps