> 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/project-roles.md).

# Project Roles

Every member of a Cogram project has a role: **Owner**, **Lead**, **Member**, or **Viewer**. Roles control what a user can see and do within a project.

Project roles are separate from [Organization Roles](/administration/organization-roles.md), which control what a user can do across the entire organization, including creating and managing projects.

## Role Overview

| Permission                             | Owner | Lead | Member | Viewer |
| -------------------------------------- | :---: | :--: | :----: | :----: |
| View meetings, reports, and files      |   ✓   |   ✓  |    ✓   |    ✓   |
| Download files and export reports      |   ✓   |   ✓  |    ✓   |    ✓   |
| View project members                   |   ✓   |   ✓  |    ✓   |    ✓   |
| Create meetings, reports, observations |   ✓   |   ✓  |    ✓   |        |
| Upload and delete files                |   ✓   |   ✓  |    ✓   |        |
| Edit drawings                          |   ✓   |   ✓  |        |        |
| Update project settings                |   ✓   |   ✓  |        |        |
| Add and remove project members         |   ✓   |      |        |        |
| Delete project                         |   ✓   |      |        |        |

## Roles in Detail

### Owner

Full control over the project. Owners can manage project settings, add or remove members, and create or edit any content.

### Lead

A management role for people who run a project day to day without owning it. Leads can do everything a Member can, plus edit and delete drawings and change project settings. In **Owner** asset-visibility mode, Leads see all project content, just like Owners.

Leads cannot add or remove members, respond to access requests, or delete the project. Those actions stay with Owners.

> **Availability**: The Lead role is available to organizations that have it turned on. If you don't see it in the role list, it isn't enabled for your organization yet.

### Member

Can view all project content and create new content (meetings, reports, observations, files). Cannot manage project settings or membership.

### Viewer

Read-only access. Viewers can view and download content but cannot create, edit, or delete anything. Useful for external stakeholders or clients who need visibility without edit access.

> **Note on meeting visibility**: What meetings a Viewer can see also depends on the project's **asset visibility** setting. In **Full** mode, Viewers see all project meetings. In **Owner** or **Restricted** mode, Viewers only see meetings they own or participated in. See [Asset Visibility](/administration/asset-visibility.md) for details.

> **Viewer is not the same as View & Respond.** The project **Viewer** role (above) controls what a user can do inside one project. **View & Respond** is an organization-level access level that controls which modules a user is licensed for. See [Licensing](/administration/licensing.md).

## Assigning Roles

Owners assign roles when inviting a user to a project, or change them later in **Project Settings > Members**. Leads, Members, and Viewers can't change roles.

## Group Access

You can assign an entire [group](/administration/groups.md) to a project in **Project Settings > Members and Groups**. All members of the group automatically get access to the project as **Members**. The **Owner** and **Lead** roles can only be assigned to a person directly, not through a group.

Group-assigned users appear in a separate **Via groups** section in the members list. Their access is managed through the group; to remove a user's access, remove them from the group rather than from the project directly.

If a user is both directly added to a project and a member of an assigned group, their effective role is the higher of the two: a user directly added as **Owner** keeps the Owner role even if their group only grants Member access.


---

# 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/project-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.