> ## Documentation Index
> Fetch the complete documentation index at: https://docs.weelkit.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Organization settings

> Set up your organization's profile, CMS, article fields, AI, AI visibility, integrations, editorial policy, visual identity and tools.

Open **Organization settings** in the sidebar. Its submenu starts with **Overview**, which has a card for each page. What you see depends on your role:

| Role | Pages |
| - | - |
| **Admin** | **Organization**, **CMS**, **Article Fields**, **AI & Agents**, **AI Visibility**, **Security**, **Teams**, **Integrations**, **Editorial**, **Visual**, **Tools** |
| **Managing Editor** | **Teams** (active members and invitations), **Integration** (with the CMS connection), **AI visibility**, **Editorial Policy** |
| **Designer** | **Settings** in the sidebar, with the visual settings only |

Writers and Editors don't have organization settings. Managing Editors can invite people in **Teams**, but can't change existing members' roles, remove members or manage custom roles. Security and Teams have their own pages: [Organization security](https://docs.weelkit.com/settings/organization-security.md) and [Team and roles](https://docs.weelkit.com/settings/team-and-roles.md).

## Organization

* **Organization Details:** the **Organization ID**, display and legal names, website, description, avatar, region, industry and company size.
* **Public Website Index:** your public **Sitemap URL**, with its status. Weelkit uses your sitemap to suggest internal links to your own pages, and to confirm the public address of articles you publish.
* **Notifications:** **Editorial Notifications** (articles and comments) and **System Alerts** (everything else) turn those notifications on or off for the whole organization. Each member's own [notification settings](https://docs.weelkit.com/settings/account.md#notifications) apply on top. Security alerts are always delivered.
* **Contact Information:** primary and support email, and phone number.
* **Localization:** default language, timezone, date and time formats, and currency. Dates and times across Weelkit follow these formats.
* **Data Management** (owner only): choose **Export Data** to download your organization's records as a ZIP file. Passwords, keys and other secrets are left out. The section shows "Preparing your export…", then **Download** when it's ready; if it fails, it says why and offers **Retry**. Exporting asks you to [confirm it's you](https://docs.weelkit.com/settings/account-security.md#confirm-your-identity).

### Danger zone

Only the owner can use these actions, and both ask you to [confirm it's you](https://docs.weelkit.com/settings/account-security.md#confirm-your-identity):

* **Transfer Ownership:** choose **Transfer**, select the new owner from your active members, confirm, and choose **Request ownership transfer**. The other member must accept. Both of you keep your roles.
* **Delete Organization:** choose **Delete**, type the organization's name, and choose **Delete organization**. The organization closes to all members immediately, and its data is permanently deleted 24 hours later.

The deletion dialog lists what is deleted: articles, versions and comments; collaborative documents; chats and saved writing; AI memory and Knowledge; members, roles and invitations; settings, CMS setup and integrations; analytics and AI visibility data; and uploaded logos. Billing records, support tickets and records of data export and deletion requests are kept for legal and support reasons.

## CMS

Connect the CMS Weelkit sends your articles to: [**WordPress**](https://docs.weelkit.com/integrations/wordpress/setup.md) (self-hosted, with the Weelkit Plugin), [**WordPress.com**](https://docs.weelkit.com/integrations/wordpress-com/setup.md), [**Sanity**](https://docs.weelkit.com/integrations/sanity/setup.md), [**Ghost**](https://docs.weelkit.com/integrations/ghost/setup.md) or a [**Custom API**](https://docs.weelkit.com/integrations/custom-api/overview.md). Managing Editors find the connection under **Integration**.

1. Choose **Connect CMS**, choose the provider, and enter its connection details or sign in with it. Choose **Connect**.
2. Choose the destination: the site (WordPress.com), and the post, document or content type Weelkit publishes to.
3. Map Weelkit's article fields to the CMS's fields, and choose **Save mapping**.
4. Set the publishing defaults:
   * **Default status:** **Draft** or **Published**. The editor's CMS button follows it. See [Send to your CMS](https://docs.weelkit.com/articles/checks-and-publishing.md#send-to-your-cms).
   * **When the article already exists:** **Ask before updating** opens a confirmation on a later send; **Always update existing** updates the same item; **Always create a new item** creates another one. See [Send to your CMS](https://docs.weelkit.com/articles/checks-and-publishing.md#send-to-your-cms).
5. Choose **Verify test draft**. Weelkit uses your mapping to publish and read back a draft in your CMS. You can inspect it there, or choose **Delete draft**.

You can choose **Finish later** at any step and continue from the connection's **Continue setup** button.

Once connected, the connection shows its status. **Manage Connection** opens its details. Use **Test connection** to check access, **Destination** to choose the content type or **Refresh destination fields**, and **Publishing defaults** to change how articles are sent. Changes to the mapping or defaults need **Verify test draft** again.

When the connection needs authorization again, **Reconnect** renews access to the same site or dataset while keeping the mapping and published links. **Disconnect** removes local credentials and setup; CMS posts stay in the CMS. Resolve unconfirmed sends and test-draft cleanup before disconnecting.

The [Integrations](https://docs.weelkit.com/integrations/overview.md) tab of these docs covers each provider in detail.

## Article fields

* **Default fields:** choose which fields Weelkit generates for every new article. Turning a field off affects future articles only.
* **Custom fields:** choose **Add field** to add a field every article carries into publishing: its **Label**, **Field type**, whether it's **Required for every article**, a **Description**, a **Generation instruction** for the AI and a **Default value**. Choose **Create field**. Use the move up and down buttons to set the order editors see, and **Edit** to change a field. Turn a field's switch off to stop using it, and on again to bring it back. A field's type can't be changed after it's created.

## AI and agents

The **AI & Agents** tab sets your organization's own AI rules and limits:

* **Enable AI Features:** turns all AI work in the organization on or off.
* **Usage Limits & Alerts:** the **AI Behaviour Level** (**Strict**, **Balanced** or **Creative**: how strictly the AI follows organization guidance), the **Warning Threshold** and **Critical Threshold** for usage alerts, and the **Alert Channels** (**Email**, **In-app**) they go to.
* **Role Based AI Access and Limits:** for each role, including custom roles, whether it can use AI, its monthly token limit, and its warning threshold. A role's limit can't be higher than the organization's.
* **Organization Wide Usage Cap:** a monthly token limit for the whole organization, with the current usage and when it resets. When it's reached, AI work pauses for everyone until it resets or an admin raises it.
* **Enforcement & Visibility:** a summary of how these rules apply.

## AI visibility

What [AEO & GEO](https://docs.weelkit.com/metrics/aeo-and-geo.md) looks for, and how often it checks. Admins and managing editors can change these settings.

* **Organization identity:** the **Organization name**, **Aliases**, **Owned domains**, **Products and topics**, **Audience** and **Positioning**. An answer is **Mentioned** when it names you or an alias, and **Cited** when it links a page on an owned domain.
* **Competitors:** up to 20 organizations, each with its name, aliases and domains. Only these count as competitors in AI answers; every other cited site stays a source. Choose **Add competitor** or **Remove competitor**.
* **Monitoring schedule:** how often **Regular questions** (daily, weekly or monthly) and **Priority questions** (daily or weekly) are checked, the **App samples per check**, and when to **Mark results stale after**. New prompts are checked straight away; later checks follow this schedule.
* **Search visibility schedule:** choose **Search visibility** to set how often Weelkit runs the searches behind the [Visibility](https://docs.weelkit.com/metrics/aeo-and-geo.md#visibility) page (daily, weekly or monthly). It runs separately from the AI answer checks.
* **Prompt suggestions:** turn **Automatic suggestions** on or off, and choose the **Suggestion cadence** and the **Maximum suggestions per run**. Weelkit suggests only prompts backed by evidence, so a run can suggest none.

Choose **Save Settings** to save, or **Discard** to undo your changes.

## Integrations

Admins open **Integrations**, with **CMS** (see [CMS](#cms)), **Analytics** and **API Webhook**. Managing Editors open **Integration**, with the same connections and controls they can use.

* **Google Analytics** and **Google Search Console:** choose **Connect** and sign in with your Google account. Then, from the card's menu, choose **Configure**, pick the **GA4 property** or **Search Console site**, and choose **Save Configuration**. To start straight away, choose **Sync** under **Sync analytics data**: it saves the source and imports the last 30 days. Weelkit then keeps the data in sync, and after Search Console's first sync it also imports up to 16 months of its history. The data feeds [Performance](https://docs.weelkit.com/metrics/performance.md) and [Analytics](https://docs.weelkit.com/metrics/analytics.md), and Search Console queries also inform [prompt suggestions](https://docs.weelkit.com/metrics/aeo-prompts.md#suggestions) in AEO & GEO. The card's menu also has **Test connection**, **Sync data**, **Reconnect Google account** (when authorization is required again) and **Disconnect**.
* **API Webhook:** choose **Add webhook** to add an HTTPS endpoint that receives signed notifications when article versions are created. The signing secret is shown once. From the endpoint you can **Send test**, see **Deliveries**, **Edit**, **Rotate secret** or **Delete** it. See [API webhook](https://docs.weelkit.com/integrations/webhook/setup.md).

Slack and Gmail are personal connections, in [Account settings → AI Preferences](https://docs.weelkit.com/settings/account.md#ai-preferences).

## Editorial

The editorial policy the AI follows when it writes for your organization:

* **Global Editorial Guidelines:** your audience and the guidelines every piece follows.
* **Style Guide:** readability, spelling variant, headline case, **Writing rules** (rules to follow and things to avoid) and **Forbidden Phrases**.
* **Category Level Rules:** choose **Add New Category**, then turn on custom rules for it to override the global guidelines for that category, with its own writing tone, audience level and style guide. Admins and managing editors can apply a category to a chat with **Select category**.

Managing editors edit the same policy from **Editorial Policy**.

## Visual

* **Brand Identity:** your brand name, primary and secondary colours, and accent colours.
* **Logos & Brand Assets:** upload logo variants, and set the default watermark (position and opacity) for the [Watermark tool](https://docs.weelkit.com/images/tools.md#image-tools).
* **Logo Usage Guidance**, **Image Style Guidance & Presets** and **Consistency Guidance:** advice given to the AI for visual work. They guide image generation; they don't enforce it.

## Tools

**Tool Availability** turns each tool on or off for the organization: **RSS Aggregator**, **Image Resize**, **Aspect Ratio**, **Image Crop**, **Watermark** and **Overlay**. Members see only the tools that are on, and the AI can use only those tools. A new organization starts with **RSS Aggregator**, **Image Resize**, **Aspect Ratio** and **Image Crop** on.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.