Settings

Settings is one screen with four groups. The menu item opens Profile, the one page every role has. Each entry is shown only to the roles that can use it, so nobody clicks an entry and gets an error page; the page itself still checks the role.

Group	Entries	Who sees them
My account	Profile · Security · Language · Display · Notifications	Everyone
Workspace	General · Team · Plan and billing (with the Extra services tab) · Defaults for new AI employees	Owner and admin. Plan and billing: the owner only.
Human takeover	Availability and alerts · Saved replies · Tags	Availability: owner and admin. Saved replies: owner, admin and editor (they can write them). Tags: every team member.
Connections	Integrations · API tokens · AI keys	Owner and admin. AI keys only when your platform turned them on for you.

Platform staff see My account and Platform instead; they manage workspaces from the platform admin.

My account

• Profile — your name, email address, and deleting your account.
• Security — password and two-factor authentication. It asks for your password first.
• Language — the language of the dashboard.
• Display — light, dark or your system setting, for this dashboard only. It was called Appearance; that name now belongs to the AI employee's tab that sets how the chat looks on your website.
• Notifications (/settings/notifications) — how you hear about things, split out of Profile: Receive live chats (visitors who ask for a person can be routed to you while a dashboard tab is open), Email me unanswered questions (off, immediately, daily or weekly; owners and admins only), browser push notifications and WhatsApp. Saving your name on Profile no longer touches these.

Workspace

• General (/settings/workspace) — the workspace name, shared learning, and the address of your public knowledge base.
• Team (/settings/team) — invite people, change a role, remove someone (it asks first). See Team members & roles.
• Plan and billing (/settings/billing) — your plan, usage and invoices. Its second tab, Extra services (/settings/billing/services), holds the one-time services that used to be Add-ons in the menu. See Plan and billing and Extra services. Trial and usage warnings stay on every page, and the upgrade card stays at the foot of the menu.
• Defaults for new AI employees (/settings/widget) — the look, voice and starter questions a new AI employee starts with. Apply to all lists exactly what it will replace before it does.

Human takeover

• Availability and alerts (/settings/availability) — business hours, whether visitors see the team member's name, and the Slack or Teams alert when someone asks for a person. See Live human handoff.
• Saved replies (/settings/saved-replies) — replies your team drops into a live chat in two clicks. They were called canned replies.
• Tags (/settings/tags) — labels for conversations.

Connections

• Integrations (/settings/integrations) — Slack, webhooks, Google, Notion and WordPress. The knowledge sources of an AI employee keep their links to it.
• API tokens — tokens for the sources API.
• AI keys — your own model keys, when enabled. See BYOK.

Old addresses

Pages that moved keep their old address; it forwards to the new one with its filters (302, so a rollback never strands a bookmark):

Old address	Now
/app/members	/settings/team
/app/integrations	/settings/integrations
/app/billing	/settings/billing
/app/billing/addons	/settings/billing/services
/app/settings/live-chat	/settings/availability
/app/settings/canned-replies	/settings/saved-replies
/app/settings/tags	/settings/tags
/app/inbox, /app/inbox/{lead}	/app/leads, /app/leads/{lead}
/app/analytics and its pages	/app/results and its pages
/app/tickets, /app/tickets/{ticket}	/app/conversations/follow-ups, /app/conversations/follow-ups/{ticket}

The form endpoints behind these pages kept their addresses (for example POST /app/members), so a tab left open during an update still saves.