> For the complete documentation index, see [llms.txt](https://thecontentforge.gitbook.io/thecontentforge-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://thecontentforge.gitbook.io/thecontentforge-docs/admin-guide/initial-setup.md). # Initial Setup This is the checklist for an admin standing up a fresh organization on TheContentForge. ### 1. Sign in as the Owner If you bought a Starter or Pro plan through self-serve checkout, your account was created as the workspace **Owner** - confirm by checking the role badge in the bottom-left of the sidebar. For Enterprise and Custom deployments, TheContentForge provisions the first Owner during onboarding. ### 2. Configure org-level settings Open **Settings** and set: * **Org name and identity** - what shows in the sidebar header * **Approval workflow** - whether posts need approval before publishing, if your plan includes it * **Optional integrations** - any tailored integrations available to your org Use [My Account > Social Connections](/thecontentforge-docs/feature-guides/social-connections.md) to connect X for analytics and publishing (Instagram and Facebook support is coming soon). ### 3. Define your Brand Voice Don't ship anything through Content Forge until [Brand Voice](/thecontentforge-docs/feature-guides/brand-voice.md) is dialed in. Take 15 minutes to: * Write 2-3 sentences describing your voice * Add 3-5 example posts that represent your brand at its best * List forbidden phrases and tone constraints ### 4. Invite your team TheContentForge is invite-only - there is no request/approve queue. From **Settings > Team Members**: * Enter each teammate's email and pick a role: Member, Editor, or Admin (see [User Roles](/thecontentforge-docs/getting-started/user-roles.md)) * Existing accounts are added immediately; new users receive an email invitation * Track unaccepted invitations in the **Pending Invites** panel See [Managing Users & Roles](/thecontentforge-docs/admin-guide/users-and-roles.md) for the full flow. ### 5. Establish the weekly cadence Pick someone (usually an Editor) to own the Monday upload of analytics through [Data Ingestion](/thecontentforge-docs/feature-guides/data-ingestion.md). The Dashboard and Patterns both depend on fresh data, and connected profiles can supplement manual uploads through [My Account > Social Connections](/thecontentforge-docs/feature-guides/social-connections.md). ### 6. Tell the team Share the login URL, the GitBook docs link, and the in-app FAQ. Let people know who their Admin is for support. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://thecontentforge.gitbook.io/thecontentforge-docs/admin-guide/initial-setup.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.