> For the complete documentation index, see [llms.txt](https://docs.linuxfoundation.org/lfx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/operations/user-permissions.md).

# User permissions

This page shows all users that have been granted access to a project. If a user is not listed here, they may have inherited permissions from a parent project. If you need to grant access to a user, or something does not look right, please contact support.

Each User listing will show their name, email, LF Account username, and the Roles provided.

Common Roles available to be assigned to users are:

* LF Program Manager - This is an "Admin" role for LF Staff and has full rights to Edit the project and any child projects. Admins may also edit anything for the project including Meetings, Mailing Lists, Committees, Domains, EasyCLA etc. The only thing an Admin does not have full rights to is the Project Definition section.
* Community Program Manager - This is an "Admin" role for non-LF Staff and has full rights to Edit the project and any child projects including EasyCLA.
* Meetings Coordinator - This role gives edit access to only the Meetings section for only the current project. This role should be selected to limit a user's capability to only meeting management.
* CLA Program Manager - This role gives edit access to only the EasyCLA section for only the current project.
* Viewer - This role gives access to view the project.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.linuxfoundation.org/lfx/project-control-center/v2-latest-version/operations/user-permissions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.