Account and Settings
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.
- Open Settings from the workspace or project menu.
- Store settings appear only when you open Settings from inside a project.
- Match the workspace or store name in the settings sidebar before editing. Personal controls appear under your account 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
- In the intended workspace or project, open its menu.
- Select Settings.
- Confirm the Workspace: workspace name selector, then choose a page under that group, Store: store name, or your account name. Opening Settings inside a store can start on Store General.
English callouts highlight the controls. Select the image to enlarge it.
Match the workspace and store headings before choosing a page. The account controls sit below these groups.
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. |
| Your account name → My Settings | Choose language, weekly performance emails, and interface sounds. | Preferences save; language changes reload the current localized page. |
| Your account name → API Keys | Create credentials for programmatic access. | The full secret appears once; revoke is destructive. This page is conditional. |
Choose the right scope
- Use Workspace for members, shared Credits, plan, and billing.
- Use Store for the current storefront, domain, scripts, and project Agent settings.
- Use Personal for your own profile, language, and API keys.
- 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.