---
title: "Types of roles and their permissions in Onesait Platform"
canonical: "https://onesaitplatform.refined.site/space/DOCT/2220819419/Types%20of%20roles%20and%20their%20permissions%20in%20Onesait%20Platform"
format: markdown
---
> Macro (toc)

# Introduction

Onesait Platform uses roles to assign permissions to users. Each of these roles is configured to be able to access and/or interact with the different components of the Platform.

The main roles and their use are listed below.

# Types of Roles

## Main roles of the Platform

- **USER (ROLE_USER)**: This role has access in query mode to the Platform; that is, it can consult information on the Platform generated by other users, but not upload information. It can therefore consume Dashboards, REST APIs, consult Entities, etc.
- **DEVELOPER (ROLE_DEVELOPER)**: This role can use all the Platform's functionalities without restrictions (Dashboards, REST APIs, IoT, etc.). It is the default user of the Platform, and the one that is created by default. It has limited access to artificial intelligence capabilities to control the instance's resource consumption.
- **ANALYTICS (ROLE_DATASCIENTIST)**: This role extends the capabilities of the ‘Developer’ role, allowing access to the analytical and artificial intelligence tools, and therefore has access to DataFlow, Notebooks, LLM flow management, etc.
- **ADMINISTRATOR (ROLE_ADMINISTRATOR)**: This role has administration access to the Platform Control Panel, from where it can manage all the concepts of an instance of the Platform created by the rest of the users, including management of users, Entities, permissions, etc.

## Internal roles

Internally, Onesait Platform manages a set of roles that enable the operation and management of a Platform installation. These roles are:

- **DEVOPS (ROLE_DEVOPS)**: This role is responsible for managing the Platform's CI/CD process. It has access to the Jenkins that is managed from the Platform, from where it can launch the compilation and version generation pipelines, both of the Platform and of verticals and microservices deployed on the Platform.
- **OPERATIONS (ROLE_OPERATIONS)**: This other role only has access to the Platform monitoring tools, being able to know the status of each module and being able to generate alerts from them.
- **SYS_ADMIN (ROLE_SYS_ADMIN)**: This third role has system administration access, allowing access to the underlying infrastructure of the Platform.

## Other roles

In addition, there are two further roles with special characteristics. These are:

- **VIEWER (ROLE_DATAVIEWER)**: This role is a subrole of the ‘**User**’ role, it only allows access to Dashboards and Marketplece.
- **PARTNER (ROLE_PARTNER)**: This role contributes to the Platform ecosystem by being able to create solutions that are marketed together with the solution (such as the Smart Home or Smart Waste solution) and therefore has all the permissions of the ‘Analytics’ role plus access to a part of the Platform operation console to be able to deploy and operate its vertical.
- **USER_APL (ROLE_USER_APL)**: This role is for those Application users who do not want to have access to the Control Panel, but who do want access to the Application managed by the Platform in which they have been registered and to its resources. This role is described in detail in the following article:

[https://onesaitplatform.atlassian.net/wiki/spaces/DOCT/pages/4873912328/](https://onesaitplatform.atlassian.net/wiki/spaces/DOCT/pages/4873912328/)

# Summary

Below is a summary table with the Onesait Platform modules and their different functionalities, and which roles may or may not interact with them.