Settings

The Settings surface is where you configure everything per- user and (for admins) per-tenant. Organized into five top-level sections plus an admin-only sixth.

Sections

Profile

Your identity inside the tenant:

  • Name (display + full)
  • Email
  • Role (sales, content, ops, admin, etc.)
  • Avatar
  • Timezone
  • Locale

Changes here update the USER namespace (see User namespace) — so the agent immediately respects your new timezone, locale, etc.

Preferences

How the agent behaves for you:

  • Output style — Brief / Detailed / JSON / Markdown table / Voice.
  • Language preference — auto-detect or explicit (en, es, fr, de, etc.).
  • Working hours — used by notification batching + scheduled actions.
  • Notification channels — email + push opt-ins per category.
  • Profile context — free-text pinned context the agent always has access to.

Integrations

OAuth + API connections (see Integrations):

  • Google — Gmail, Calendar, Drive
  • Microsoft — Outlook, Teams, OneDrive
  • GitHub — repos, issues
  • Ayrshare — social posting (LinkedIn, X, IG, FB, TikTok)
  • MCP servers — generic Model Context Protocol connections

Each integration shows its connection status, last sync, scopes granted, and a disconnect button. Disconnecting revokes the OAuth token immediately.

Skills

The tenant's skill library (see Skills concept):

  • Browse by group (Platform default / Tenant-authored / Proposed).
  • Edit tenant-authored skills inline.
  • Accept/reject promoted skill proposals.
  • View version history for any skill.

Agent runs

Personal run history:

  • Last 100 runs, filterable by surface, outcome, date.
  • For each run: full prompt, tool calls, subagent tree, token usage, cost (cloud), citation density.
  • Replay a run with edits ("redo with output style = JSON").

Tenant (admin only)

  • Tenant profile — org name, NAICS code, primary region.
  • Members — user list, invite flow, role assignment.
  • Tasks → Auto-confirm — per-action-kind allowlist.
  • Today — card-type registry, cron schedule, filler ratio.
  • Dashboards — per-module default layouts, freshness thresholds.
  • Skills — author + propose new platform-default-like skills scoped to this tenant.
  • Billing (cloud) — plan, payment method, invoices, usage.
  • Audit log (cloud Enterprise tier) — all member actions, exportable.
  • Privacy / DSAR (cloud Enterprise tier) — data export + delete requests.

The super-admin portal (cloud only)

The platform super-admin portal at admin.<basedomain> is separate from Settings. It manages the multi-tenant platform itself — cross-tenant analytics, feature flags, tenant provisioning, compliance workflows. Self-host operators don't have this portal (no platform/tenant separation in self-host); see Self-host vs cloud for the full inventory of edition differences.

Realtime sync

Changes in Settings propagate via Realtime — if you have Settings open in two tabs and edit Profile in one, the other reflects the update without refresh. Same for admin changes affecting all members (e.g. an admin changing the tenant's working hours preference propagates to all members in real time).

Version-locked defaults

Tenant-level defaults (Today registry, dashboard layouts, auto-confirm allowlists) are version-locked to the platform release they were set under. When a release adds new card types or auto-confirm options, admins see a "What's new in this release" banner in Settings → Tenant prompting them to opt into the new options (rather than getting them automatically and surprising the team).

Read next

  • Today — the surface whose card registry you configure in Settings → Tenant → Today.
  • Integrations → OAuth — the most-used Settings section after Profile.