Administer Labor0

Manage workspace access, credentials, notifications, usage, and billing in Labor0.

Before you begin

Confirm the workspace and the responsibility for the change. Have a second reviewer for broad membership, credential, security, or billing changes when your team’s process requires one.

Admin paths

Need	App path	Expected evidence
Invite people or define workflow target groups	Settings > General > Members or User groups	A member or invitation shows its role and state; a group shows its workflow-target membership
Create API access	Settings > Runtime > Tokens	A named token appears without revealing its secret again
Configure runtime authentication	Settings > Runtime > Runtime credentials	The provider row reports configured state without showing the value
Register passkeys or trusted review bots	Settings > Billing & Security > Security	Passkey readiness or the allowlist count changes
Enable browser wake-ups	Settings > General > Notifications	Current browser ready is `On` and workspace setup is `Synced`
Review plans, usage, and payment readiness	Settings > Billing & Security > Billing	Execution eligibility, plan, period, and totals are visible

Use members and groups, tokens and credentials, security and notifications, or usage and billing for the complete procedure.

Member roles grant access. User groups provide stable targets for approvals, attention, and notifications; adding someone to a group does not grant Workspace or Project permission.

What ready looks like

The workspace name matches the intended scope and the saved result is visible on the same settings page. Never copy a token, passkey material, payment identifier, or private recipient.

Permission guidance

Administrative controls are role-aware. Billing, membership, credential, and security controls may have different owners; use the app’s permission message as the source of truth.

Continue in the app

Open Labor0 and select workspace settings.

If an admin change is blocked

Symptom: a setting cannot be saved. Likely cause: the actor is not authorized, a prerequisite is missing, or the current workspace is not the intended one. Safe recovery: verify scope, read the app’s next-step message, and ask the correct owner to make the change.