Account settings
Account and Preferences open the same Settings window. Use the grouped sidebar on desktop or the section selector on mobile to navigate. The familiar entry points and keyboard shortcuts remain available; visible sections depend on the active context and your org role.
Personal vs organisation context
Use the context switcher in the app header to act as yourself or as an organisation. User-scoped resources such as sessions, preferences, LLM connections, automations, Git providers, API keys, secrets, skills, agents, rules, MCP config, hooks, and history are read and written in the active context.
In org context, admins manage shared configuration. Managers and members can use shared resources, but admin-only surfaces such as shared LLM connections and shared daemon keys are restricted.
Settings navigation
| Group | Sections |
|---|---|
| General | Appearance, Shortcuts |
| Account | Profile / Org, Billing, History / Org History, Orgs (personal context) |
| Models | LLM, Mixes |
| Connections & automation | Git connections, Integrations, Automations |
| Workspace defaults | Git identity & attribution, Docker |
| Security | API Keys, Secrets |
| Daemon configuration | Plugins, MCP, Hooks, Guidelines, Skills, Agents, LSP |
Paths in these docs such as Account → LLM and Preferences → MCP refer to sections in this shared Settings window. Git connections are separate from Git identity and attribution under Workspace defaults. This navigation change does not change permissions, personal or organisation scope, or where settings are stored. Daemon configuration still targets the selected machine; project and checkout settings remain separate.
Account configuration
| Section | Purpose | Notes |
|---|---|---|
| Profile / Org | Shows the signed-in user or active organisation identity. | Org profile includes organisation name, slug, and ID. |
| Automations | Create saved schedules and authenticated webhook endpoints. | Org automations are shared and can be filtered by owner. |
| LLM | Configure model connections and subscription providers. | Org members/managers cannot edit shared LLM settings. |
| API Keys | Create daemon pairing keys. | Raw tokens are revealed once; existing rows may only show a hash. |
| Git connections | Connect GitHub App installations and Git OAuth providers. | See Git providers. |
| Billing | View plan, limits, trial state, seats, and checkout/portal links. | Personal and org billing are scoped separately. |
| History | Browse archived sessions, export transcripts, restore, or clean up. | Org managers/admins can filter history by member. |
| Secrets | Store secret values for MCP servers and plugin configs. | See Secrets. |
| Orgs (personal) / Org member management | Create orgs; invite members and manage their roles within Org. | Admins and managers can invite; managers can manage members only. |
Daemon API keys
API keys in AFK are daemon keys. Generate one for each laptop, CI runner, staging server, or shared daemon that should connect to the hub. Copy the raw token immediately; AFK does not guarantee it can show the raw token again later. If a key is exposed or a machine is retired, revoke it and create a replacement.
Org roles
| Role | Can do | Restricted from |
|---|---|---|
| Admin | Manage shared LLM, daemon keys, Git providers, org secrets, members, billing, automations, and history cleanup. | System-level operations outside organisation settings. |
| Manager | Supervise org sessions, manage member workflows, view/filter org history, and use shared config. | Admin-only shared configuration such as shared LLM and API keys. |
| Member | Use available shared resources, run sessions, receive assignments, and accept handoffs. | Most shared configuration and org-wide administrative actions. |