> For the complete documentation index, see [llms.txt](https://docs.apolo.us/index/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apolo.us/index/apolo-console/getting-started/projects.md). # Projects Projects are units of collaboration on a platform. Each Apolo platform artifact e.g. job, storage file, image, app instance, etc. belongs to some project. Users could invite other users into their project specifying access level (reader / writer / manager / admin). Refer to `apolo admin` for project administration and to `apolo config switch-project` to, well, switch between projects. Most of Apolo CLI accept `--project` flag to perform various commands in corresponding projects. ### Project roles Project contributors could have one of available roles: reader, writer, manager or admin. Each subsequent role expands on the previous one. #### Reader Readers are only able to read project artifacts: download / read storage, blobs, check job statuses and logs, access workloads via HTTP endpoints, pull images, etc. #### Writer User with this role is able to perform updates of artifacts -- write new files or update existing in storage or blobs, run new workloads or terminate existing, push images, etc. #### Manager Project managers could also invite other users into projects, promote/demote their roles up to manager access level. #### Admin Administrators are able to remove project, promote/demote administrators. When you create project, you become it's administrator. --- # 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.apolo.us/index/apolo-console/getting-started/projects.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.