> For the complete documentation index, see [llms.txt](https://docs.bito.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bito.ai/help/account-and-settings/managing-user-access-levels.md). # Managing user access levels Understanding User Roles in Bito Workspaces A Bito Workspace represents your organization. It is the highest level of organization in Bito. In a Bito Workspace, different user types play distinct roles in managing and collaborating within the workspace. Here is an overview of the three user types: **Owner, Admin, and User**. Understanding these roles will help you effectively manage your workspace and optimize team collaboration. **Owner:** The Owner holds the highest level of authority within the workspace **Admin:** Admins have a significant role in managing the workspace alongside the Owner **User:** Users have access to the workspace with limited administrative privileges Here's a table summarizing the roles of the different user types in a Bito Workspace:

	Owner	Admin	Member
Make or Remove Other Owner	Yes	No	No
Promote another user to admin or remove admin	Yes	Yes	No
Manage Subs and Billing	Yes	Yes	No
Manage Overage Limits	Yes	Yes	No
Add Member by E-mail	Yes	Yes	No
Access and Share Join workspace link	Yes	Yes	Yes
Deactivate Member	Yes	Yes	No
Edit WS Settings - Name, Discovery	Yes	Yes	No
Approve Member [When joining from the "Invite Workspace" web link]	Yes	Yes	No
Force Reauthentication	Yes	Yes	No

--- # 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.bito.ai/help/account-and-settings/managing-user-access-levels.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.