> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/concepts/workspace-management/seats-and-shared-permission-groups-in-ui-bakery.md).
# Seats & Shared permission groups in UI Bakery
There are three types of seats available in UI Bakery: **Developer, End-user** & **Shared permission groups**. Developers and End-users be assigned individual roles and permissions, giving you granular control over access to apps, data sources, and pages.
* A team member on a *Developer* seat can develop, deploy and edit apps, as well as manage users (depending on the role assigned).
* A team member on an *End-user* seat can use the applications assigned to his role, but NOT edit or develop them.
* A *Shared permission group* (SPG, unlimited seats) is a special type of custom user role that can include **Use-only** permissions for apps and data sources.
{% hint style="info" %}
Shared permission group is available only in the *Low-code* mode.
{% endhint %}
## Shared permission group, explained
If you have any questions regarding our Shared permission group, check out this section for a quick explanation:bulb:
A Shared permission group, as mentioned before, is basically a special type of custom user role. If you assign users to this group, they will have only **Use** permissions for apps and data sources.
* One SPG can include an **unlimited** number of users - so if you have a large group needing the same permissions, you can use a single Shared Permission Group for them.
* If you assign users ONLY to SPGs, they won't be included in the count of End-user seats.
* You have to pay for each SPG separately - for example, if you have two large groups of *internal* and *external* users (requiring different permissions), you'll need to buy two SPGs for them.
* SPGs are better suited for users needing the same level of access, so opt for standard End-user seats if you need really granular permissions and access.
* You can use both SPGs and End-user seats together, no limitations here. That is actually the approach we recommend to make the most of our pricing options.
To sum it up, Shared permission groups are perfect for large user groups (25 and expanding) with the same permissions.
Make sure to check our [blog post](https://uibakery.io/blog/ui-bakery-pricing-explained) for a more detailed explanation of UI Bakery pricing model based on specific use scenarios. We hope it helps!
---
# 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.uibakery.io/concepts/workspace-management/seats-and-shared-permission-groups-in-ui-bakery.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.