For the complete documentation index, see llms.txt. This page is also available as Markdown.

Members

Members lists everyone who can reach this project, and it is where you decide what they can do inside it.

Access works at two levels. Everyone carries an organization role that applies across every project by default. The project role on this page overrides it here and nowhere else, starting at None, which means inherit.

That override is what most real access decisions come down to. A contractor who is a Member across the organization can be dropped to View Only on a production project without touching their access anywhere else. Someone who needs to deploy on one project can be raised there alone, rather than across everything. An Owner is the exception: neither role can be changed here, since ownership is organization-wide.

Both roles are set from the row itself, as is removing someone from the project. Invite Members brings someone new in. The same people appear on Team at the organization level, which shows their organization role without the per-project override, and that is where the roles themselves are explained.

Last updated

Was this helpful?