# Managing Users & Roles

User and role management lives on the **Users** page, available only to Admins.

### Approving a new user

1. The user submits a Request Access form on the login page
2. They appear in **Users** with a **pending** badge
3. As Admin, click their entry
4. Choose **Approve** and assign a role (Member / Editor / Admin)
5. They can now sign in with full access for that role

If the request shouldn't be approved (wrong org, doesn't belong, etc.), choose **Decline**. The user will see a message on their next sign-in attempt.

### Changing a user's role

1. Find the user on the **Users** page
2. Open the role dropdown next to their name
3. Select the new role
4. The change takes effect immediately on their next page load

### Removing a user

1. Find the user on the **Users** page
2. Choose **Remove**
3. The user loses access to your org immediately

Removed users keep their TheContentForge account but no longer belong to your organization.

### Role guidance

* **Member** - anyone who needs to draft content, view performance data, or work from the shared content surfaces
* **Editor** - anyone responsible for keeping data fresh, monitoring bot logs, or auditing security
* **Admin** - small handful of people who own org configuration and access decisions

A common shape for a 5-10 person team: 1-2 Admins, 1-2 Editors, the rest Members.

### Audit trail

Every approval, role change, and removal is recorded in the [Security Log](/thecontentforge-docs/feature-guides/security-log.md). When in doubt about who changed what, that's the source of truth.


---

# 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/users-and-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.