> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/administration/organization-roles.md).

# Organization Roles

Every user in a Cogram organization has one of three organization-level roles: **Owner**, **Admin**, or **Member**. These roles control what a user can do across the entire organization, including creating and managing projects.

Organization roles are separate from [Project Roles](/administration/project-roles.md), which control what a user can do within a specific project.

## Role Overview

| Permission                             | Owner | Admin | Member |
| -------------------------------------- | :---: | :---: | :----: |
| Access and view their own projects     |   ✓   |   ✓   |    ✓   |
| Create new projects                    |   ✓   |   ✓   |   ✓ ¹  |
| View any project in the organization   |   ✓   |   ✓   |        |
| Update settings on any project         |   ✓   |   ✓   |        |
| Archive or delete their own projects   |   ✓   |   ✓   |   ✓ ¹  |
| Delete any project                     |   ✓   |   ✓   |        |
| Create, edit, or delete project types  |   ✓   |   ✓   |        |
| Invite and remove organization members |   ✓   |   ✓   |        |
| Manage SSO, billing, and integrations  |   ✓   |   ✓   |        |
| Assign and remove the Admin role       |   ✓   |       |        |

¹ Members can create, archive, and delete their own projects by default. An org Admin or Owner can restrict these actions to Admins and Owners only. See [Project Management Permissions](/administration/project-management-permissions.md).

## Roles in Detail

### Owner

Full control over the organization. Owners can manage all projects, invite or remove members, configure integrations, and assign or revoke Admin roles. There is typically one Owner per organization.

### Admin

Organization-wide administrator. Admins can create, update, and delete any project in the organization, even projects they are not a member of. Admins can also invite members and manage organization settings, but cannot assign or revoke Admin roles. This role is suited for project managers or operations leads who need to oversee the full project portfolio.

### Member

Standard organization user. Members can create new projects and access any project they have been added to. They cannot view, modify, or delete projects they have not been invited to, and have no access to organization administration settings. An org Admin or Owner can optionally [restrict project creation, archiving, and deletion](/administration/project-management-permissions.md) to Admins and Owners only.

## How Organization Roles Interact with Project Roles

When an Owner or Admin accesses a project, they have full administrative rights over that project regardless of whether they have been explicitly added as a project member. This allows Owners and Admins to manage the project portfolio without needing to be listed on every project.

For Members, access to a project's content is governed entirely by their [Project Role](/administration/project-roles.md) (Owner, Lead, Member, or Viewer) within that project.

## Groups

Groups let you organize users by team, department, or office location and assign project access in bulk. See [Groups](/administration/groups.md) for full details on creating groups, managing membership, and how group-based project access works.

### Group Admin is not an organization role

The **Group Admin** badge is a per-group capability, not an organization role. It can be granted to any user in the organization (including Members, Admins, and Owners) and the user keeps their existing org role. A Group Admin can manage members and settings for the specific groups they administer, but has no organization-wide authority. See [Group Admin Role](/administration/groups.md#group-admin-role) for details.

## Assigning Organization Roles

Organization roles are managed in [Organization Settings > Users](https://app.cogram.com/dashboard/settings/admin/users). Only Owners can assign or remove the Admin role.


---

# 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.cogram.com/administration/organization-roles.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.