> For the complete documentation index, see [llms.txt](https://docs.cloudio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudio.io/managing-roles-and-users/working-with-roles-and-users/typeofroles.md).

# Understanding the types of roles

The CloudIO platform provides a default Administrator role when it is set up. Additionally, the CloudIO platform has the following predefined roles that can be assigned to users:

## Administrator

A user with the administrator role has the permissions to:

* manage the application setup
* create new roles and users
* create subdomains

## Developer

A user with the developer role has the permissions to create new datasources and pages.

## Patch Manager

A user with the patch manager role has the permissions to create and apply patches of the application components.

## Site Developer

A user with the site developer role can make cosmetic changes to the application if the solution built on the CloudIO platform is implemented at the customer site.

**Limitations for Site Developer Role:**

1. Has read-only access to **Manage Datasources**
2. Cannot create a new page but can redesign the existing one
3. Cannot create custom workflow nodes

## Site Administrator

A site administrator can make changes in setup, add new users and assign existing customized roles to these users if the solution built on the CloudIO Platform is implemented at a customer site.

**Limitations for Site Administrator**

1. Cannot create any role
2. Can create user and assign customized roles to the user, but not the pre-defined platform roles
3. Can schedule request by selecting customized roles


---

# 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.cloudio.io/managing-roles-and-users/working-with-roles-and-users/typeofroles.md?ask=<question>&goal=<endgoal>
```

`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.