For the complete documentation index, see llms.txt. This page is also available as Markdown.

Settings Reference

The Settings hub groups workspace, team, account, and Telegram controls. Admin-only tabs appear only for users with the right role.

Hub tabs

  • General - org-level configuration for Admins and Owners

  • Team Members - user management for Admins and Owners

  • My Account - personal profile, wallet, billing history, and Social Connections

  • Telegram - Bot History, Security Log, and (admins) a Settings tab with bot health and the chat/user allowlists

Organization

  • Org name - what shows in the sidebar header and email branding

  • Org identity - logo and visual identifiers (where supported)

Platform integrations

Connect the platforms your team operates on:

  • X (Twitter)

  • Instagram (coming soon)

  • Facebook (coming soon)

These integrations power Data Ingestion, Algorithm Watch signals where applicable, and Competitor Intelligence.

Org-specific integrations

Some integrations are scoped to a single org by design - they're tailored solutions, not platform-wide features. If you don't see an integration described here, it's intentionally not enabled for your org.

Approval Workflow

For plans that include it, admins can gate outgoing posts behind review:

  • Enable approval workflow - toggle on/off for the org

  • Minimum approver role - pick Editor, Admin, or Owner; posts awaiting approval can only be approved by users at or above this role

  • Auto-reconcile manual posts - when enabled, posts you have marked as manually confirmed are automatically synced into analytics so the Dashboard and Patterns reflect them alongside posts published through the app

Approval actions play out on the Calendar, not Settings - Settings only configures the gate.

Telegram Bot

Telegram bot configuration - the live health check, Allowlisted Chat IDs, and Allowlisted User IDs - lives under Settings → Telegram → Settings (admin-only). See the dedicated Telegram Bot guide for commands, allowlisting, and setup.

Usage limits

Settings surfaces your plan's current usage against its limits - users, social profiles, competitor sources, active experiments, brand voice profiles, Telegram channels, and analytics retention. If you're close to a cap, Settings is where you'll see it first. Limits are governed by your plan. Contact support if you need help with a limit.

Redo onboarding

If your org needs to re-run the Onboarding Wizard - for example after a major positioning change - Settings has a Redo onboarding option that returns you to the wizard with your current values preserved as defaults. Use it sparingly; ad-hoc edits to Brand Voice, Goals, and Audience can be done in their dedicated pages without resetting the flow.

Web3 project panel

Org type Web3 Project unlocks a dedicated panel for project-level fields (profile, positioning, team, roadmap, FAQs, objections) and a Updates / Changelog section for shipped releases. See Web3 Projects.

What you won't find here anymore

  • Site access password - removed. Access is now controlled entirely through user accounts and roles.

Best practices

  • Only enable integrations you actually use - fewer surfaces, fewer surprises

  • Document any integration credentials in your team's password manager, not in chat

  • If you change a credential, verify the next Data Ingestion succeeds before assuming all is well

Last updated

Was this helpful?