> For the complete documentation index, see [llms.txt](https://docs.skyone.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skyone.cloud/english/skyone-studio/overview/settings-and-preferences/users-and-permissions.md).

# Users and Permissions

In the “**Users and Permissions**” menu, you can view, add, edit and delete users in a workspace, as well as create groups and change user permissions.&#x20;

To access this area, go to “**Settings**” and then “**Users and permissions**”.&#x20;

Follow the documentation below according to the tabs:

* [Users](#usuarios)
* [Groups](#permissoes)
* [Permissions](#permissoes-3)

### Users <a href="#usuarios" id="usuarios"></a>

In the "**Users"** tab you can see the following options and information:

**Search for users:** search for a user by a specific name in the search bar

**Name**: list of users who have access to the space and their respective emails below.

**Status**: indicates the status of the invitation, with the following types of user status:

* **Active**: the user has activated the account.
* **Waiting**: when the invited user has not yet accessed the space.

**Permission**: the type of authorization the user has in the workspace, with the following types of permission:

* **Administrator**: configures access and payment, creates and edits information, etc.
* **Owner**: the person who created the workspace.
* **Developer**: can create and edit modules, flows and integrations.

#### Invite user

To invite a user, follow these steps:

1\) At the top of the "**Users**" tab, click the "**Invite user**" button. The following modal will appear:&#x20;

<figure><img src="/files/osaf8he9Eexo2lBZWMS6" alt=""><figcaption></figcaption></figure>

2\) Enter the email and choose the permission type. Then, click "**Invite**".

3\) The invited user will receive an email to access the workspace.

#### Resend Invitation <a href="#reenviar-convite" id="reenviar-convite"></a>

If a user has been added to a workspace but has not yet created an account, you can resend the invitation. To do this, simply click "**Resend invitation".**

<figure><img src="/files/NModlvA9EIocmYG4IU7t" alt=""><figcaption></figcaption></figure>

If the invited user already has an account in **Skyone Studio**, you can not only resend the invitation but also remove the user using the "**Delete**" option. When you click it, a confirmation modal will appear to confirm the deletion.

#### Change user permission

After the invitation is accepted, meaning the user has an Active status, you can change their permission. Follow these steps:

1\) Click the arrow next to the user's permission type.&#x20;

<figure><img src="/files/wekSGcWpfAaHJgwG58rJ" alt=""><figcaption></figcaption></figure>

2\) From the list of options, choose the most appropriate one.&#x20;

3\) Confirm the action.&#x20;

&#x20;

**Remove user**

To remove a user, follow these steps:

1\) Click the arrow next to the user's permission type.

<figure><img src="/files/0HJwc5Py32j1xWLafivM" alt=""><figcaption></figcaption></figure>

2\) From the list of options, click "**Remove access**".

3\) Then, confirm the action by clicking "**Delete**".

{% hint style="info" %}
It is not possible to undo the deletion. If you regret it, you will have to add the user again.
{% endhint %}

### Groups <a href="#permissoes" id="permissoes"></a>

In "**Groups**," you can create and manage workspace groups. By default, all users in a workspace belong to the "default" group, and this group cannot be edited.

#### Concept

The "**Groups**" feature allows you to specify which workspace members have permission to manage specific items. This functionality applies to **modules**, **flows**, **integrations**, and the **API Gateway**. Additionally, if Data features are enabled, it also applies to **Data Jobs**, **File Jobs**, and **File Templates**.

#### Key Points:

* Choosing the correct group is crucial to ensure user access. Without the appropriate permissions, a user won't be able to view or manage certain items.
* Flows follow the integration hierarchy. This means that if an integration is set to be accessed only by the "XY" group, this setting also applies to related flows.
* Despite being accessed in Flow Canvas, Data Studio does not follow the integration hierarchy. In other words, there is no linkage when choosing the groups that can manage **Data Job, File Job,** and **File Template** resources.
* When executed manually in **Flow Canvas** with a **Data Job** or **File Job** component that the user doesn't have access to, the execution uses the group saved for that Data Job/File Job, not the user's group.

{% hint style="info" %}
[Use case: using Groups to manage access to flows](/english/skyone-studio/how-to/use-case-using-groups-to-manage-access-to-flows.md)
{% endhint %}

#### Create a group <a href="#permissoes" id="permissoes"></a>

To create a group, follow these steps:

1\) In the "**Groups**" tab, click "**Create a new group**".

2\) Fill in the "**name**" and "**description**" fields. Then, click "**Create**".

{% hint style="warning" %}
The name and description cannot be changed after the group is created.
{% endhint %}

3\) That's it! The group will appear in the "**Groups**" tab.

<figure><img src="/files/C931Ar2QnR04R4ZzMdm4" alt=""><figcaption></figcaption></figure>

#### Adding a user to a group <a href="#permissoes" id="permissoes"></a>

To add a user to a group, simply click on the names in the drop-down list, and you can add one or several users simultaneously.

<figure><img src="/files/EDQgkL4jQPaXKQ0iQTfd" alt=""><figcaption></figcaption></figure>

#### **R**emoving a user from a group

To remove a user from a group, simply click on the “x” icon to the right of their name.

<figure><img src="/files/McVu0EmziymGR7EeCY71" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
It is not possible to delete users from the *Default* group.
{% endhint %}

#### Delete group

To delete a group, simply click the **"Delete Group"** button next to the **Add Users** button for the group in question.<br>

Then, type the group's name to confirm the action.

<figure><img src="/files/StDieMd25OFaqE06vScZ" alt=""><figcaption></figcaption></figure>

### Permissions <a href="#permissoes" id="permissoes"></a>

The "**Permissions"** tab allows you to view the existing permissions in that space, the number of users in each type of permission and manage the types of actions allowed.

<figure><img src="/files/3Unjmg65kwirQJwUBR0g" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
This option is only available to workspace administrators.
{% endhint %}

#### Types of permissions <a href="#tipos-de-permissoes" id="tipos-de-permissoes"></a>

There are two types of permissions: **Admin** and **Developer**.

* **Admin**: can create, edit and delete any information in the workspace. They also have access to administrative tasks such as Usage and Payment.
* **Developer**: Can develop integrations but does not have access to administrative tasks.

{% hint style="info" %}
You cannot create custom permissions.
{% endhint %}

The right-hand corner of each permission shows the number of users with this permission.

#### **Managing permissions**&#x20;

By clicking on each type of permission, it is possible to check more details, as well as edit the allowed actions of the permission.&#x20;

<figure><img src="/files/rvtNx2n2CG2BWNGjykSG" alt=""><figcaption></figcaption></figure>

**Edit permissions**&#x20;

To edit the permission's allowed actions, click on “**Edit**”. You can then enable or disable the permissions options.&#x20;

<figure><img src="/files/vabaticaa1qIQMddnNjY" alt=""><figcaption></figcaption></figure>

The following categories can be edited:

**Workspace users**

* **Add users to the workspace:** Allows you to add a new user to the workspace.
* **Authorize users in the workspace:** Allows you to authorize new users.
* **Change user permission:** Allows you to change the type of user permission within the workspace.
* **Delete users from the workspace:** Allows you to reject or exclude a user from the workspace.

**Connected Account**

* **Create connected account**: allows you to create a connected account.
* **Edit connected account:** allows you or other people to edit connected accounts.
* **Delete connected account**: allows you to delete any connected account.

**API Gateway**

* **Create API Gateway:** allows you to create a new API Gateway.
* **Edit API Gateway:** allows you to edit API Gateways created by you or others.
* **Delete API Gateway:** allows you to delete any API Gateway.

**API Gateway Users**

* **Create API Gateway user:** allows you to create an API Gateway user.
* **Edit API Gateway user:** allows you to edit an API Gateway user
* **Delete API Gateway user:** allows you to delete an API Gateway user

**Integrations**

* **Create integration:** Allows you to create a new integration.
* **Edit integration:** Allows you to edit an integration created by you or others.
* **Delete integration:** Allows you to delete any integration.

{% hint style="info" %}
The owner administrator, in other words the creator of the workspace, can add or remove permissions from the administrators of the workspace.

Administrators, on the other hand, can add or remove permissions for developers in the workspace.
{% endhint %}

After making any changes, click on "**Save changes"**.

{% hint style="warning" %}
Changes to permissions will only be applied after users reload the page.
{% endhint %}

#### View permission users <a href="#visualizar-usuarios-da-permissao" id="visualizar-usuarios-da-permissao"></a>

After clicking on "**View all"**, you can see the list of users with the permission.

<figure><img src="/files/9TEkVhqVFD9RoLsnqfUp" alt=""><figcaption></figcaption></figure>


---

# 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.skyone.cloud/english/skyone-studio/overview/settings-and-preferences/users-and-permissions.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.
