Skip to main content

Changes to User Management

This section covers changes between release on the following topics:

  • Authorization to the platform

    • User roles

    • Permissions of roles

  • Required permissions

  • Authentication methods

  • User management

Release 7.10

Fine-grained sharing permissions on individual objects

Beginning in this release, you can change the permissions to a shared object for individual users. These fine-grained permissions can be assigned at the time of sharing by the object's Owner or a workspace admin. They can also be changed at a later time.


Workspace-level permissions that are defined through a user's assigned roles still apply. These permissions define the maximum and default level of permissions that can be assigned when an object is shared.


In this release, fine-grained sharing permissions apply to flows and connections only.

For more information, see Overview of Sharing.

Release 7.5

Roles Management

Beginning in Release 7.5, workspace administrators can create and assign roles to workspace users. Each role contains zero or more privileges.

  • A role is a set of privileges that you can assign to workspace users. Workspace users may have one or more roles.


    Each current user or newly created user is automatically assigned the default role, which grants a set of privileges for all governed object types in the workspace.

  • A privilege is a level of access to a type of user-defined workspace object, such as flows.

Roles are created and assigned through the Roles page in the Admin console. For more information, see Roles Page.

Workspace owner role is removed

As of Release 7.5, the workspace owner role has been removed from user access.

The privileges of this role have been collapsed into the admin role for workspaces, which has full capability to administer the workspace.

Authorization Overview

Workspace roles govern access to workspace objects.

Platform roles govern access to platform capabilities.

For more information on these distinctions, see Overview of Authorization.