Project roles and their rights are not explained fully in documentation

[ClaudioFriederich]

Select Topic Area

Question

Feature Area

Projects

Body

In https://docs.github.com/en/issues/planning-and-tracking-with-projects/managing-your-project/managing-access-to-your-projects the documentation talks of read, write, admin roles for projects. But, it is not explained what exactly these roles entail. On the corresponding pages for Repository and Organization roles, there is a matrix of what precise rights each role encompasses. Such a matrix is missing from the documentation on project roles. For example, does adding an item to a project require write access to a project, or is write access to the project required only for, say, creating new views or changing workflows? What does project admin rights include that write rights does not? A matrix is needed to expound these details.

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬