> ## 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.

# Roles and permissions

> What each organization role can do, and how sharing an article or writing gives people access to it.

Two things decide what you can do in Weelkit: your **organization role**, and your **access to each document**.

## Organization roles

Admins choose each member's role in [Organization settings → Teams](https://docs.weelkit.com/settings/team-and-roles.md).

| Role | What it's for |
| - | - |
| **Writer** | Chat with the AI; create articles and writings, and edit the ones they own or were given edit access to; use Knowledge, images and tools. Writers don't see Metrics or organization settings. |
| **Editor** | Everything a Writer does, plus read all of the organization's articles and writings, publish, and see **Performance**, **Analytics** and **AEO & GEO**. |
| **Managing Editor** | Everything an Editor does, plus add and change prompts in AEO & GEO, and four areas of **Organization settings**: **Teams** (view active members and invite people), **Integration** (including the CMS connection), **AI visibility** and **Editorial Policy**. |
| **Admin** | Full control of the organization: profile, CMS, article fields, AI settings, AI visibility, security, members and roles, integrations, editorial policy, visual identity and tools. |
| **Designer** | Images, image tools, a personal chat with the AI (**Weelkit AI**), and the organization's visual settings (brand identity, logos and watermark). |

Every role has its own [Account settings](https://docs.weelkit.com/settings/account.md). Saving images edited with the [image tools](https://docs.weelkit.com/images/tools.md#image-tools) needs design access, which Admins and Designers have.

The person who creates an organization is its **owner**, and starts with the Admin role. Only the owner can delete the organization or transfer ownership. When ownership moves to another member, both keep their roles.

Admins can also create **custom roles** with their own name, description and permissions. See [Team and roles](https://docs.weelkit.com/settings/team-and-roles.md#custom-roles).

## Access to an article or writing

Each article and writing has its own members, managed from **Members** in the editor. See [Work together](https://docs.weelkit.com/articles/collaborate.md#share-an-article-or-writing).

| Document role | Can |
| - | - |
| **Owner** | Edit, comment and manage who has access. The person who created it is always an owner. |
| **Editor** | Edit and comment. |
| **Commenter** | Read and comment. |

People whose organization role can read all content (Editors, Managing Editors and Admins) can read every article and writing without being added, and can manage its members.

Anyone who can read an article can open it in their own chat and ask the AI about it. If they can't edit it, the AI can read the document but won't change it, and the chat says so.


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