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

# Roles and Permissions

> Understanding the different permission levels in OpenHands Organizations.

## Overview

Organizations in OpenHands support three roles, each with different levels of access and capabilities:
**Member**, **Admin**, and **Owner**. This page describes what each role can do.

## Permissions Table

| Permission                  | Member | Admin | Owner |
| --------------------------- | :----: | :---: | :---: |
| Create conversations        |    ✓   |   ✓   |   ✓   |
| Manage private settings     |    ✓   |   ✓   |   ✓   |
| Invite users                |        |   ✓   |   ✓   |
| Elevate users to Admin role |        |   ✓   |   ✓   |
| Add credits                 |        |   ✓   |   ✓   |
| Modify LLM settings         |        |   ✓   |   ✓   |
| Elevate users to Owner role |        |       |   ✓   |
| Claim Git organizations     |        |       |   ✓   |
| Delete organization         |        |       |   ✓   |

## Role Descriptions

### Member

Members are the default role for users joining an organization. Members can:

* **Create conversations** - Start new conversations using the organization's shared credits.
* **Manage their own private settings** - Configure settings that are only visible to them, including:
  * MCP servers
  * Secrets
  * API keys
  * Git user settings
  * Slack integration

Members cannot invite new users, modify organization-wide settings (like LLM settings), or manage other users' roles.

### Admin

Admins have all the capabilities of Members, plus the ability to manage the organization's settings and users. Admins can:

* Everything a Member can do.
* **Invite users** - Send invitations to new team members.
* **Change user roles** - Promote Members to Admin or demote Admins to Members.
* **Add credits** - Purchase and add credits to the organization's shared pool.
* **Modify LLM settings** - Configure the default LLM provider and model for the organization.

Admins cannot delete the organization or claim Git organizations.

### Owner

Owners have full control over the organization. Owners can:

* Everything an Admin can do.
* **Delete the organization** - Permanently remove the organization and all associated data.
* **Claim Git organizations** - Link specific Git organizations to route OpenHands resolver requests to this organization.

<Note>
  Every organization must have at least one Owner. If you need to transfer ownership, first promote another
  user to Owner before changing your own role.
</Note>

## Private Settings

Regardless of role, all organization members have control over their own **private settings**. These settings
are personal to each user and are not visible to other organization members, including Admins and Owners.

Private settings include:

* **MCP Servers** - Configure Model Context Protocol servers.
* **Secrets** - Store sensitive values like API tokens and credentials.
* **API Keys** - Manage keys for programmatic access to OpenHands.
* **Git Settings** - Configure personal Git authentication and preferences.
* **Slack Integration** - Connect your personal Slack workspace.

## Next Steps

* [Managing Members](/openhands/usage/cloud/organizations/managing-members) - Learn how to invite and manage users.
* [Organization Settings](/openhands/usage/cloud/organizations/settings) - Configure organization-wide settings.