> For the complete documentation index, see [llms.txt](https://docs.interactive.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.interactive.ai/settings/members.md). # 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. --- # 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.interactive.ai/settings/members.md?ask=&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.