Workspace Settings

Workspace settings are accessible from the Settings link in the left navigation. The page has four tabs: General, Members, Tokens, and GitHub Integration. Only owners and admins can modify most settings.

General

Settings → General

Set the workspace name and URL slug.

The workspace name appears in the header and in email notifications. The slug is the URL identifier — changing it immediately redirects all existing URLs to the new path. Only owners and admins can save changes here.

Workspace name

Display name shown in the app header and notifications.

Slug

The URL segment after /app/ — e.g. changing it to acme makes your board available at planwright.tools/app/acme. Lowercase letters, numbers, and hyphens only.

Plan & Billing

Settings → General

View your current plan and upgrade when you need more seats or longer audit retention.

Free

3 seats

30-day audit retention

Good for solo engineers or small experiments.

Team

$15 / seat / mo

10 seats

1-year audit retention

For teams shipping with agents regularly.

Business

$39 / seat / mo

50 seats

1-year audit retention

For larger orgs that need more capacity.

Only the workspace owner can change the plan. Billing is handled via Stripe — clicking Upgrade redirects to a Stripe-hosted checkout page. Cancellation is available from the Stripe Customer Portal.

Members

Settings → Members

Invite team members and manage their roles.

Members are invited by GitHub username. The invite appears as pending until the user logs in with GitHub OAuth for the first time. Owners and admins can change roles and remove members at any time.

owner

Full control: can change the plan, rename the workspace, manage all members (including other owners), and connect or disconnect the GitHub App. Each workspace has exactly one owner.

admin

Can invite and remove members, change member roles (up to admin), and manage MCP tokens. Cannot change the plan or disconnect the GitHub App.

member

Can view and interact with the board, claim objectives, and use the MCP server. Cannot manage members or settings.

viewer

Read-only access to the board. Cannot claim objectives or use the MCP server.

MCP Tokens

Settings → Tokens

Generate a personal token for CI pipelines, service accounts, or headless agents.

Each workspace member has one personal MCP token. Tokens are shown once at generation time — store them in your secret manager immediately. Regenerating a token invalidates the previous one and terminates any active MCP connections using it.

For interactive use on your own machine, OAuth is the recommended path — no token needed. The browser opens for GitHub login on first connect, then the connection is cached. Use tokens only for CI or headless environments where a browser flow is not possible.

OAuth (recommended)

claude mcp add planwright --transport http https://mcp.planwright.tools/mcp

Service token (CI / headless)

claude mcp add planwright \
  --header "Authorization: Bearer <your-token>" \
  https://mcp.planwright.tools/mcp

Owners and admins can view and revoke any member's token from the All MCP Tokens panel at the bottom of the Tokens tab. Audit records attribute actions to the token creator.

GitHub Integration

Settings → GitHub

Connect the Planwright GitHub App to your organization.

Connecting the GitHub App allows Planwright to receive webhooks for PRs and commits, link agent-authored code to the objectives that produced it, and populate the audit chain with verified contribution records. Only the workspace owner can connect or disconnect the App.

1.
Install — Click Connect GitHub in Settings. A popup opens to the GitHub App installation page. Select your organization and grant access to the repositories you want Planwright to track.
2.
Select repos — You can grant access to all repositories or specific ones. Planwright only receives webhooks for repos you explicitly grant access to.
3.
Verify — After installation, the Settings page shows Connected with your GitHub org name and the list of accessible repositories.

Disconnecting removes the webhook integration. Existing audit records are preserved. To fully uninstall, also remove the app from your GitHub organization settings.

← GitHub Integration Beyond Engineering →