> For the complete documentation index, see [llms.txt](https://docs.sprintsq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprintsq.com/settings/organizations.md). # Organizations * **Company:** Tells about the subscription plan, its validity, number of users, and projects involved in it * **Users:** Gives basic information about the members of your company. Users can be added to respective projects or removed only by the admin (i.e.) user with setting update permission access. Admin can only update the information about the other user. A user with prior access can only view the records of the respective projects. * **Projects:** Gives information about the various projects present in the company. Projects can be created and modified only by the Admins and users with setting update permission access. * **Roles:** When a user is added to SprintsQ, he/she can access the SprintsQ modules based on their roles. By default admin and Guest user roles will be created once you sign up. You can create a custom role with a set of permissions and assign the role to a user in user sections. There are 4 permission modes for each module - view, create, update, and delete. --- # 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.sprintsq.com/settings/organizations.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.