> For the complete documentation index, see [llms.txt](https://docs.clarity.vote/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clarity.vote/clarity-v1/participating-in-an-organization/admin-actions/manage-membership-badges-and-permissions.md).

# Manage Membership, Badges, and Permissions

Many actions on the Clarity Platform require users to have some form of permission to take an action. There are 4 main user types that can interact with an Organization on the Clarity Platform.\
\
**Visitors:** Users who have not completed an Organization's New Member Application Workflow

**Members:** Users who have completed an Organization's New Member Application Workflow

**Badge Holders:** Members who have earned a specific badge, which is used to grant specific permissions in the Organization.

**Admins:** Users who have the ability to take all actions available on the Clarity Platform.

Organization admins can customize where each of these 4 user types can visit and which actions they can take by assigning members specific Badges and configuring Permissions associated with those Badges.


---

# 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://docs.clarity.vote/clarity-v1/participating-in-an-organization/admin-actions/manage-membership-badges-and-permissions.md?ask=<question>&goal=<endgoal>
```

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