# Settings Reference The **Settings** page is admin-only and groups org-level configuration. ### 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 * Facebook These integrations power [Data Ingestion](/thecontentforge-docs/feature-guides/data-ingestion.md), [Algorithm Watch](/thecontentforge-docs/feature-guides/algorithm-watch.md) signals where applicable, and [Competitor Analysis](/thecontentforge-docs/feature-guides/competitor-analysis.md). ### 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 in `approval_pending` can only be approved by users at or above this role * **Auto-reconcile manual posts** — when enabled, posts marked `confirmed_manual` 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](/thecontentforge-docs/feature-guides/calendar.md), not Settings — Settings only configures the gate. ### Telegram Bot The Telegram Bot section shows live health status for the bot webhook. See the dedicated [Telegram Bot](/thecontentforge-docs/admin-guide/telegram-bot.md) 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 and any super-admin override. ### Redo onboarding If your org needs to re-run the [Onboarding Wizard](/thecontentforge-docs/getting-started/onboarding-wizard.md) — 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](/thecontentforge-docs/feature-guides/web3-project.md). ### 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](/thecontentforge-docs/feature-guides/data-ingestion.md) succeeds before assuming all is well --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/admin-guide/settings-reference.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.