> For the complete documentation index, see [llms.txt](https://docs.tessl.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessl.io/introduction-to-tessl/organizations-workspaces-and-roles-for-users.md).
# Organizations, Workspaces, and Roles for users
## How Organizations, Workspaces, and Roles work in Tessl
**Organizations** are top level entities, often representing the billing or corporate entity, with a subcategory called **Workspaces** that provide role-based access to the various users across the company. Your administrators will create workspaces and provide access based on [Roles](/administrators/roles.md) tessl provides.
Certain actions, like evaluations and publishing are performed from the CLI to the Tessl platform, and your ability to perform these functions will depend on the **Role** assigned, and workspace you have associated with the task you are trying to accomplish. Similarly access to skills, and certain features in the web interface will also be determined by what Organization or Workspace are selected and the roles associated.
When creating Plugins, publishers will publish plugins to the Workspaces they have access to Publish to, similarly Consumers or other roles can search for Plugins that are public or in a workspace where they have permissions.
## Navigating Organizations
If you have access to an Organization, or multiple Organizations, clicking your account on the bottom left will display an interface that allows switching. If you do not yet have an organization or been invited to one, you may be prompted to create one.
\
## Navigating Workspaces
Once in the correct Organization, the selector on the side menu will display the workspaces you have access to, with the capabilities your Role allows:\
---
# 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.tessl.io/introduction-to-tessl/organizations-workspaces-and-roles-for-users.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.