User Management

nuvo Data Pipelines give you full control over managing Users within your organization and allow you to create Sub-organizations for your customers. Within your organization, Users can have different roles, such as Member or Owner, each with varying levels of rights. You can also define custom permissions for each User, ensuring precise control over who can create new pipelines, edit input/output connectors, manage pipeline executions, and more. Sub-organizations let your customers create and manage their own pipelines and components, keeping them separate from those used internally by your organization. Meanwhile, users in your organization maintain full access across all pipelines and Sub-organizations—limited only by the permissions assigned to them.

Organization

As an organization you have two different ways of managing your Users. You can use the nuvo Pipelines API (1) or you can use the nuvo User Platform (2). On the User Platform you can invite new Users to your organization, update User information and their permissions, and also remove Users as needed.

General access rights of organizations

Unlike Sub-organizations, Users of your organization have access to the nuvo User Platform and can therefore besides managing Users (depending on their role) also see the number of executions as well as access your organization's license key which is e.g. required to authenticate with the nuvo API.

Users in your organization, depending on their individual permissions, can access and manage all pipelines and components (connectors, TDMs) within your organization. They can also view all pipelines and components across your sub-organizations.

Additionally, Users can create pipeline templates, allowing you to predefine settings and configurations for new pipelines, streamlining the setup process.

When creating connectors and target data models, you can choose between two visibility settings:

• PRIVATE – Accessible only to you and other Users within your organization. Sub-organizations will not have access.
• PUBLIC – Available to all your sub-organizations, making it easy to share standardized components across teams.

This flexibility ensures that you have full control over how pipelines and components are shared within your organization and beyond.

User roles

Users of your organization can have two different roles. They can be an Owner (1) or a Member (2).

Owner

Owners are Users of your organization with more adiministrative rights than members. Owners have the following user management rights:

• Invite new Owners
• Update Owners
• Invite new Members
• Update Members
• Create new sub-organizations
• Update sub-organizations
• Delete users (owners, members, or sub-organizations except for themselves)

For each Owner, the permissions to manage pipelines and their components can be set indvidually. You can set the permissions for the following components:

• Pipelines
• Executions
• Connectors
• Target Data Models (TDM)

For each of those components, you can set permissions for the following actions:

• create (create a new pipeline, connector, execution, or TDM)
• view (view a pipeline, connector, execution, or TDM)
• update (update a pipeline, connector, execution, or TDM)
• delete (delete a pipeline, connector, or TDM)

By default, when an Owner is created via the nuvo API or the nuvo User Platform, all permissions are set to true unless modified during creation.

Member

Members are Users within your organization who have limited administrative rights for user management but retain the same granular permissions for managing pipelines and their components. Members have the following user management rights:

• Invite new Members
• Update Members
• Create new Sub-organizations
• Update Sub-organizations
• Delete Sub-organizations

For each Member, the permissions to manage pipelines and their components can be set indvidually. You can set the permissions for the following components:

• Pipelines
• Executions
• Connectors
• Target Data Models (TDM)

For each of those components, you can set permissions for the following actions:

• create (create a new pipeline, connector, execution, or TDM)
• view (view a pipeline, connector, execution, or TDM)
• update (update a pipeline, connector, execution, or TDM)
• delete (delete a pipeline, connector, or TDM)

By default, when a Member is created via the nuvo API or the nuvo User Platform, all permissions are set to true unless modified during creation.

Create a new user in the nuvo User Platform

To invite a new User, log into the nuvo User Platform and go to the Organization page.

Steps to invite a new user:

• Click "Invite New User" in the Organization section.
• Enter User Details – Provide the user's email address, first name, and last name. By default, the email address serves as the user’s identifier, but you can change it if needed (learn more about identifiers here).

Select a role & position:

• Role: Choose between Member (limited admin rights) or Owner (full admin rights).
• Position: Select the User's role within your organization (e.g., C-Level, Customer Success, Product Manager, Developer). If none fit exactly, choose the closest match.

Set permissions:

• If you want to use the default permission settings, simply click "Send Invitation".
• To customize permissions, go to the "Permissions" tab. Here, you can define whether the User can create, view, update, or delete pipelines, executions, connectors, and target data models.

Sub-organizations

Creating and managing Sub-organizations enables your customers to independently use nuvo's embeddable pipeline components, while ensuring their data remains securely separated from other customers.

For each Sub-organizations the permissions to manage pipelines and their components can be set indvidually. You can set the permissions for the following components:

• Pipelines
• Executions
• Connectors
• Target Data Models (TDM)

For each of those components, you can set permissions for the following actions:

• create (create a new pipeline, connector, execution, or TDM)
• view (view a pipeline, connector, execution, or TDM)
• update (update a pipeline, connector, execution, or TDM)
• delete (delete a pipeline, connector, or TDM)

By default, when a Sub-organization is created via the nuvo API or the nuvo User Platform, all permissions are set to true unless modified during creation except for the permissions to create, update, view, and delete target data models which are set to false by default.

General access rights of Sub-organizations

Unlike Users in your organization, Sub-organizations do not have access to the nuvo User Platform. Instead, they can manage their pipelines exclusively nuvo's embeddable pipeline components.

Sub-organizations can access and manage only the pipelines, connectors, and TDMs they create. However, they can also use any connectors and TDMs that a user from your organization has set to PUBLIC. This ensures flexibility while keeping access control in place.

Create a new Sub-organization in the nuvo User Platform

1. Log into the nuvo User Platform and go to the Organization page.
2. In the Organization section, select "Sub-Organizations" to view a list of all existing Sub-organizations.
3. Click "Add Sub-Organization" to create a new one.
4. Enter a Name and Identifier – Assign a unique name and identifier for the Sub-organization (learn more about identifiers here).
5. Set Permissions:
   • To use the default permission settings, simply click "Add".
   • To customize permissions, navigate to the "Permissions" tab, where you can define whether the Sub-organization can create, view, update, or delete pipelines, executions, connectors, and target data models.

Identifier

Every User (Owner or Member) and Sub-organization in nuvo has a unique Identifier, which serves as a distinct way to identify them within your organization.

• For Owners and Members, the identifier is automatically set to their email address by default.
• For Sub-Organizations, the identifier must be manually assigned during creation.

Identifiers do not need to follow a specific format—they can be any string of your choice. However, we recommend using an internal identifier, such as a company-specific ID, to ensure consistency and easy reference across your systems.

When using the nuvo API the identifier is used to authenticate Users and Sub-organizations. You can read more in our guide Get started with the nuvo API.