> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/administer-and-govern/control/members.md). # Members Manage project membership and the current roles that control who can operate, build and administer work in Lleverage. Members controls who belongs to a Project and which current Project role they hold. ![The Members page showing a direct Project member with editable access and organisation owners whose access is inherited via the organisation.](https://3370306531-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlgSglJDQZxDZdn20CUcl%2Fuploads%2FVPPnR6qFoVVlhMkKeTg0%2Fcontrol-members.png?alt=media) The current Project roles are: * **Owner** — full access; manage members, build and publish workflows. * **Builder** — create, edit and publish workflows; manage tables and knowledge bases. * **Operator** — run published apps, view sessions, and manage project files. A legacy `Member` role can still exist in older data, but it is not a current Project role to assign or design around. ### Direct membership versus organisation ownership A direct Project member has a Project-role selector and can be removed from the Project when the acting user has the required access. An organisation Owner can instead appear as **Owner (via organisation)**. That row has no Project-role selector because the effective owner access comes from the organisation rather than from a Project membership row. Change that person's organisation role under organisation **Settings → Members**, not on this Project page. That means Project membership alone is not the complete access model. ### Inviting people **Invite Members** is available to Project Owners and organisation Owners. Use the narrowest role that matches the person's actual operational responsibility and revisit access when ownership changes. For the current role model and its practical implications, see Roles and Permissions. --- # 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.lleverage.ai/administer-and-govern/control/members.md?ask=&goal= ``` `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.