# User Roles

There are four org roles inside an organization. For most users the day-to-day progression is Member -> Editor -> Admin, with Owner as the org-level top role.

### Member

The default role for new approved users. Members can:

* Use Content Forge and Video Forge to generate drafts
* Browse Brand Voice, Patterns, Competitor Analysis, Experiments, Asset Library, Calendar, ForgeSays, and Algorithm Watch
* View the Dashboard
* Manage their own account

Members **cannot** ingest analytics data, view Bot History or the Security Log, manage Social Connections, or change org settings.

### Editor

Everything a Member can do, plus:

* **Data Ingestion** - upload weekly analytics CSVs
* **Bot History** - view bot command logs
* **Security Log** - review security events for the org

Editors are typically the people responsible for keeping platform performance data fresh and monitoring operational logs.

Editors can also publish through already-connected publishable profiles. If the org's approval workflow is enabled, their ability to send immediately depends on the configured minimum approver role.

### Admin

Everything an Editor can do, plus:

* **Settings** - configure org-level settings and approval workflow
* **Users** - approve pending requests, assign and change roles, remove members
* **Social Connections** - connect, disconnect, and manage publish/track defaults

Admins are responsible for who has access and how the org is configured.

### Owner

Owners sit above Admins for org-level controls. They can manage the setup wizard, Social Connections, approval thresholds including **Owner only**, and the rest of the org's top-level configuration.

### Super Admin

A separate platform-level Super Admin role is used by TheContentForge staff to support multiple orgs. Super Admin is not assigned through the normal user flow.


---

# 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/getting-started/user-roles.md?ask=<question>
```

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.
