---
title: "Roles and Permissions"
slug: "roles-and-permissions"
updated: 2025-10-23T13:49:08Z
published: 2025-10-23T13:49:08Z
canonical: "docs.connect.visma.com/roles-and-permissions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.connect.visma.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Roles and Permissions

This article describes the roles and permissions that can be assigned to users in the Flows application. Understanding these roles is essential for managing access and maintaining data security.

Flows is designed for collaboration, enabling you to work on flows with your team and easily share within others.

### Administrator

The Administrator role provides full access to all Flows application functionalities. Administrators can manage user accounts, configure flows, adjust system settings like increasing the organization’s cost plan, and change the ownership of flows or connections.

### Editor

The Editor role allows users to create, view, update and delete flows and connections. This role is intended for users who actively design and modify data workflows.

### Viewer

The Viewer role grants read-only access. Users can view shared flows, monitor execution history, and retry or redrive failed executions. This role is intended for users who need to observe workflows and troubleshoot issues without modifying data or configurations.

## Sharing access to Flows vs Connections

In Flows, it’s important to understand the distinction between **Flows** and **Connections**, as they are shared and managed separately:

### **Flows**

A Flow is a data workflow that automates tasks between apps and services. Flows define *what happens* and *when*. You can share a Flow with other users in your organization, giving them access according to their role (Administrator, Editor, or Viewer). Sharing a Flow allows collaborators to view, edit, or manage its executions depending on their permissions.

### **Connections**

Connections are the credentials or integrations that Flows use to access external applications, such as Google Sheets, Slack, or Salesforce. Connections are **not automatically shared** when you share a Flow.

- If a user is granted access to a Flow, they can **interact with the steps that already use a Connection** according to their role.
- They **cannot add new steps** using that Connection in the same Flow.
- They also **cannot use that Connection in other Flows** unless explicitly granted access.

### **Sharing Access**

> [!NOTE]
> **Only the Owner of a Flow or Connection can share it with others**

- **To share a Flow:** Assign the desired user(s) to the Flow. Their Role determines what they can do with the Flow and its existing steps.
- **To share a Connection:** You must explicitly grant Editor users access to the Connection. This allows them to create new steps or use the Connection in other Flows.

This separation ensures secure credential management while allowing collaboration on existing Flows.