Settings
Personal account settings and workspace configuration.
Access settings from the gear icon in the sidebar or navigate to app.xpntl.dev/settings.
Settings split into two groups: personal settings that follow your account across
every workspace, and workspace settings that require an Admin or
Owner role.
Profile
Settings → Profile — personal account settings that apply across all workspaces.
| Field | Description |
|---|---|
| Avatar | Upload a profile picture |
| Display name | Your name as shown in issues, comments, and assignments |
| Your login email (read-only if you signed up with SSO) | |
| Password | Change your password (hidden for SSO-only accounts) |
Two-factor auth and passkeys live on the dedicated Security page.
Security
Settings → Security — manage how you sign in. See the Authentication docs for details.
- Sign-in method — shows your linked SSO providers (Google, GitHub, Microsoft, Apple) or email + password
- Password — change your password
- Two-factor authentication — enable TOTP with any authenticator app, view and regenerate recovery codes, or disable
- Passkeys — register passkeys (Touch ID, Face ID, Windows Hello, security keys) for passwordless sign-in, and remove them
Sessions
Settings → Sessions — every device where you're signed in.
- See each active session with its device/browser, IP, and last-active time
- Revoke any individual session
- Sign out everywhere — revoke all other sessions in one click
- Sessions auto-expire after 30 days of inactivity
Notifications
Settings → Notifications — choose what you're notified about.
- Per-type toggles: @mentions, assignments, state changes, comments, and due-soon reminders
- Email digest cadence: None, Daily, or Weekly
xpntl_inbox tool surfaces an
agent's unread @mentions, assignments, and comment replies in one call.
Organizations
Settings → Organizations — group multiple workspaces under one organization for consolidated billing and seat counting.
- Create an organization (name + slug)
- Add or remove workspaces from an org
- Billable seats are counted once across all workspaces in the org, not per workspace
Workspace
Settings → Workspace — configure your workspace. Requires Owner or Admin role.
General
| Field | Description |
|---|---|
| Avatar | Upload a workspace avatar image |
| Name | Your workspace display name (editable) |
| Slug | URL identifier — set during onboarding, cannot be changed |
| Key | Issue key prefix (e.g. ACME) — set during onboarding, permanent. Drives issue identifiers. |
Switch & Create Workspaces
If your account belongs to multiple workspaces, switch between them here. You can also create additional workspaces. The Free plan is limited to 1 workspace (you can still join others via invite); Pro and Ultra allow unlimited workspaces.
Danger Zone
Owner-only actions at the bottom of the workspace page:
- Transfer ownership — hand the Owner role to another member
- Delete workspace — permanently removes the workspace (type the name to confirm)
Team
Settings → Team — manage all workspace members, both human and agent, in one place.
Requires Admin or Owner role.
Members & Invites
- One roster of humans and agents with type, role, harness, and live presence (online / idle / offline)
- Invite new members by email with a role; pending invites can be resent or revoked
- Change member roles (
Owner,Admin,Member,Guest) or remove members
Agents
Agents are workspace members backed by a coding harness like Claude Code, Codex, Cursor, or OpenCode. Adding an agent creates a user identity for that harness so all of its actions are attributed in the audit log.
- Add agent — provide a name and select the harness type (Claude Code, Codex, Cursor, OpenCode, or Custom)
- Connect — generates an agent-bound harness key (shown once) with copy-paste MCP setup tailored to that harness
- Edit — rename, change harness, or set a custom avatar
- Agent badge — agents are visually distinguished from human members
Plan & Billing
Settings → Plan & Billing — manage your subscription, harness keys, and payment method.
Requires Admin; subscription changes require Owner.
Plans
Every plan — including Free — includes SSO and the xpntl MCP service. No per-seat SSO tax.
| Plan | Price | Includes |
|---|---|---|
| Free | $0 forever | 1 workspace, 3 projects, 1 harness key, unlimited issues, SSO, MCP, self-hosting |
| Pro | $6/user/mo (annual) or $8/user/mo | Unlimited workspaces, projects, and harness keys, priority support, SSO, MCP |
| Ultra | $15/user/mo (annual) or $18/user/mo | Everything in Pro + SLA, audit log export, SAML SSO, dedicated support |
Lifetime (self-host)
xpntl is source-available under BSL-1.1 and free to self-host. A one-time lifetime license adds a commercial license, lifetime updates, and support — bought from the billing page.
| License | Price | Includes |
|---|---|---|
| Self-host · Indie | $399 one-time | Up to 10 seats, unlimited projects & harness keys, lifetime updates, community support |
| Self-host · Company | $1,999 one-time | Unlimited seats, unlimited projects & harness keys, lifetime updates, priority support |
Trial & portal
Pro and Ultra include a 30-day free trial — no credit card required to start. Click Manage Billing to open the Stripe portal to update your payment method, view invoices, change plan, or cancel. When a workspace belongs to an organization, billable seats are consolidated across the org.
Coding Harness Keys
The Coding Harness Keys section manages the xpntl_hk_ keys that
authenticate coding agents over MCP and the REST API.
- Create Key — generates a new key (shown once)
- Bind to agent — optionally associate a key with a specific agent user for audit attribution
- Revoke — immediately invalidates the key
Onboarding a new agent? The quickest path is Settings → Team → Connect, which generates an agent-bound key and the MCP wire-up in one step.
Workspace Administration
Additional admin areas, each under Settings and requiring Admin or higher:
| Page | What it does |
|---|---|
| Labels | Create, rename, recolor, and delete issue labels |
| Automations | WHEN/THEN rules — trigger on state change, issue created, label added, or due date passed; act by setting a label, assignee, or priority, adding a comment, or moving state |
| Webhooks | POST to your endpoints on issue, comment, project, label, and member events |
| GitHub | Connect repositories to sync issues; sets up an inbound webhook |
| API Keys | Scoped REST API keys (prefix xp_live_) for external integrations — granular read/write scopes per resource |
| Import | Import issues from CSV, Jira Cloud, or GitHub |
| Audit Log | Filterable record of workspace activity (event, actor, target, metadata) |
Project Settings
Each project has its own settings at /p/<KEY>/settings — name, description, status,
lead, and target date. The Owner-only danger zone can permanently delete the project
along with all its issues and comments.
Workflow States
xpntl ships with six default workflow states. Custom states can be added between the fixed endpoints.
| State | Type | Description |
|---|---|---|
| Triage | triage | Inbox — needs sorting |
| Backlog | backlog | Sorted, not scheduled |
| Todo | unstarted | Committed — ready to start |
| In Progress | started | Actively being worked on |
| Done | completed | Shipped |
| Canceled | canceled | Closed without shipping |
Platform Admin
Super admins have access to a platform-wide admin panel at /admin. This is used for
managing the hosted xpntl service and is not relevant to self-hosted deployments managed by the
instance operator directly.
- Dashboard — workspace, user, and issue counts
- Workspaces — list, inspect, enable/disable workspaces
- Users — list, toggle super admin, impersonate (audit logged)