Workspace
Everything on this page lives under Settings in the console. It covers the workspace-level controls that have no page of their own: who is in the workspace, what each settings page does, and how to take your data out.
Members and roles
Every member holds one role, and owners and admins can invite teammates from Settings > Members with Invite a teammate. An invite grants the member, admin or read-only role, and pending invites count toward the member limit alongside accepted members. The Free plan includes two team members; paid plans do not cap members.
| Role | Description |
|---|---|
owner | Full control of the workspace, including deleting it. |
admin | Invites members and manages roles, deletes any API key or telemetry token, reviews published pages and requests exports. |
member | The default role for a teammate who works in the workspace. |
read-only | The lowest role, for people who need to see the workspace without running it. |
Each member also carries a set of granular permission scopes, managed from the Manage permissions card on the same page.
Join by email domain
On the Team plan and above, Joining by email domain under Settings > Members lets anyone with a verified email on your company domain join as a member without an invite. Owners and admins get an email each time someone joins this way.
Teams
Manage teams, also under Settings > Members, groups members into teams for shared ownership and visibility of resources. Create one with New team.
Settings map
| Settings entry | What it controls |
|---|---|
| Workspace | Name, slug, workspace ID, avatar and description, plus the sections in the next table. Changing the slug changes every URL in the workspace. |
| Billing & Usage | Your plan, usage against its limits, invoices and overage. See Billing and usage. |
| Members | Roles and permissions, invites, joining by email domain, and teams. |
| Coding Agents | Connect your editor's agent over MCP and create the API key it uses. See Platform MCP server. |
| Integrations | Connect and disconnect clouds, code hosts and observability tools. See Integrations. |
| Clouds | The cloud accounts agents use to inspect your infrastructure. See Clouds. |
| Repositories | The code repositories agents can read and act on. See Repositories. |
| API Keys | Scoped keys for scripts and CI. See API keys and OAuth clients. |
| OAuth Clients | Applications that access Praxen Inc. on a user's behalf. See API keys and OAuth clients. |
| Telemetry Tokens | Credentials that authenticate alerts forwarded from your observability tools. A token's creator or a workspace admin can delete it. |
| Labels | Labels that organize and categorize resources across the workspace. |
| Pages | Every public page the workspace has published, which admins and owners can review and delete. |
| Notifications | Your personal email preferences and the workspace weekly digest. See Notifications. |
| Analytics | Charts of usage, investigations, issues and autofixes over the last 7 to 90 days, hourly or daily, for all users or one person. |
| Support | Documentation, a call with the Praxen Inc. team, a Slack Connect channel and a feedback form. |
The Workspace page itself is split into sections.
| Section | What you set there |
|---|---|
| AI Models | The model family behind your agents and your own provider key. See AI models. |
| Investigations | The severity at which Praxen Inc. investigates and fixes confirmed issues on its own, and the alert signatures you have suppressed. |
| Autofix | Whether autofix pull requests open at all and whether commits are attributed to the person who asked or to Praxen Inc. |
| Escalations | The escalation severities Praxen Inc. announces right away in your Slack notifications channel and by email to admins. |
| Impact assessments | Whether each pull request gets an assessment against the production topology. See Impact assessments. |
| Privacy & data | Whether Praxen Inc. may use workspace data to improve its models, and the workspace export. |
| Screensaver | Plays your live topology fullscreen. |
| Danger Zone | Deletes the workspace. Only the owner can, and it is not reversible. |
Idle Free workspaces
A Free workspace nobody has interacted with for seven days gets a warning email, and background monitoring pauses three days later if nobody comes back. Opening the workspace or replying to the email resumes it; Billing and usage lists what pauses and what keeps running.
Export your data
Admins and owners can request an export from Privacy & data with Request export. Reports, impact assessments, settings and threads arrive in one JSON archive. You get an email with a download link when it is ready. Exports work for 60 days after workspace deletion.
Related
- Notifications to choose which events reach your inbox and what the workspace gets in Slack.
- AI models to run agents on your own provider key or endpoint.
- API keys and OAuth clients to create credentials for scripts and applications.
- Billing and usage for plan limits, invoices and idle workspaces.