---
title: Account and Settings
description: Find workspace, store, billing, usage, personal, and security controls in Runner.
---

Runner groups settings by who or what they affect: the workspace, the current store, or you. This keeps shared billing and members separate from store-specific domains and your personal profile.

## What this covers

You will know where each settings group lives and which pages require a role, plan, published store, or staged feature.

## Availability and prerequisites

- You must be signed in.
- Workspace and Personal settings are available from the workspace avatar menu.
- Store settings appear only when you open Settings from inside a project.
- On screen, the store-specific settings group is labeled **Shop: _store name_**. This guide uses **Store** as the shorter group name.
- **Profile** and **Security** are protected direct/legacy account pages that the current global avatar and Settings menus do not expose. Use them only when Runner or Runner support provides an approved entry.
- Some controls require workspace-owner or admin permission.
- Domain, API Key, and Experiments pages can be hidden or gated by plan, publication state, or staged availability.

## Open Settings

1. In a workspace or project, select your avatar in the lower-left corner.
2. Select **Settings**.
3. Choose a group and page from the settings sidebar.

## Settings map

| Group and page | Why it is useful | What happens next |
| --- | --- | --- |
| Workspace → **General** | Rename or describe the workspace. | Valid changes save automatically. The danger zone also contains Delete Workspace. |
| Workspace → **Members** | Invite people and manage active or pending access. | Owners can invite, cancel invitations, or remove members; eligible members can leave. |
| Workspace → **Plan & Billing** | Review the current plan and available billing actions. | Plan cards, confirmation, checkout, billing management, and extra-credit options appear according to account state. |
| Workspace → **Usage & Credits** | Understand balance, sources, and spending. | One date-range control updates the summary, chart, category cards, and activity feed. |
| Store → **General** | Manage the current store's identity and search appearance. | Name, Page Title, Description, favicon, watermark, and Delete Store controls appear. |
| Store → **Domain** | Connect, buy, renew, or transfer a domain. | Availability depends on plan, publication, permission, and domain state. |
| Store → **Custom Scripts** | Add JavaScript to the storefront. | Changes remain unsaved until you select **Save Changes**. |
| Store → **Agent** | Choose Skills available in this project. | You can add or disable configurable Skills for this store. |
| Store → **Experiments** | Configure automated experiment goals and traffic. | This Beta page appears only when enabled and requires a published store. |
| Personal → **My Settings** | Change your name, avatar, and interface language. | Name changes auto-save; language changes reload the current localized page. |
| Personal → **Workspaces** | Open settings for another workspace or create one. | Selecting **Settings** changes the workspace shown in the dialog. |
| Personal → **API Keys** | Create credentials for programmatic access. | The full secret appears once; revoke is destructive. This page is conditional. |

## Choose the right scope

1. Use **Workspace** for members, shared Credits, plan, and billing.
2. Use **Store** for the current storefront, domain, scripts, and project Agent settings.
3. Use **Personal** for your own profile, language, workspaces, and API keys.
4. Before a sensitive action, confirm the workspace and store names shown in the dialog.

## Common states and limits

- **Saving…** followed by **Saved** confirms an auto-save field finished.
- A disabled control can indicate missing permission, a plan gate, a store prerequisite, or an operation already in progress.
- Billing and domain pages show the current terms and amount. Do not rely on an old screenshot or copied price.
- Destructive actions require confirmation, but the exact confirmation differs by action.
- Hidden pages should not be opened through copied links unless the current interface exposes them for your account.

## Troubleshooting

- If the Store group is missing, close Settings, enter the intended project, and open Settings again.
- If a page shows an upgrade or publish-first state, complete that prerequisite only if it fits your intended workflow.
- If an auto-save fails, the previous value remains or returns; correct the field and retry.
- If you are unsure which workspace is being changed, close the dialog and reopen Settings from that workspace.
- If you need account-security help but no approved entry is visible, contact Runner support instead of guessing a direct route.

## Related guides

- [Workspace General](./workspace-general.mdx)
- [Members and invitations](../workspace/members-and-invitations.mdx)
- [Subscription plans](../plans-and-billing/subscription-plans.mdx)
- [Store General](./store-general.mdx)
- [Security and sessions](./security-and-sessions.mdx)