---
title: "On user permissions"
canonical: "https://onesaitplatform.refined.site/space/DOCT/2220823296/On%20user%20permissions"
format: markdown
---
To use Dataflow, you need to have an administrator or analytics role - although only administrators have special permissions, including being able to edit all dataflows or manage instances.  
A user who creates a dataflow is the owner of that dataflow and has full rights over it, just like an administrator.


The owner or administrator can assign permission to edit or view a dataflow by using the sharing screen.  
If you want to know how to assign permissions, click on the following link.

> ℹ️ [How to assign permissions to users](https://onesaitplatform.atlassian.net/wiki/spaces/DOCT/pages/2220823378/How+to+assign+permissions+to+users)


The editing permission has all the options available to the user: Start, stop and edit the flow.

![image](media://4d7b4b93-e09d-4f5c-b2ac-096a7e8aab20)


The display permission would be like the following image. The user cannot edit or start or stop the flow. The user can only clone it and visualize it.

![image](media://ad30e687-07da-45f9-b3ce-ed050a9b981f)



If a user decides to make a dataflow public, then that dataflow will be visible by all analytics users (since administrators can edit all of them). If a dataflow is public, **then it still does not give permissions to edit it, only to view or clone it.**

To know how to make a dataflow public, click on the following link.


> ℹ️ [How to make a Dataflow public](https://onesaitplatform.atlassian.net/wiki/spaces/DOCT/pages/2220823436/How+to+make+a+Dataflow+public)


A typical listing of an analytics user using different permissions could be like the following image.

![image](media://023d2209-1f62-48f8-9ab7-b90250655f3d)

The same list seen from an administrator would instead be like that.

![image](media://03a003c7-a910-4d57-b44d-fe3807de423f)