Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 43 Next »


Contents:

Our documentation site is moving!

For up-to-date documentation of Designer Cloud on AWS, please visit us at https://help.alteryx.com/AWS/.

   

Contents:


Feature Availability: This feature may not be available in all product editions. For more information on available features, see Compare Editions.

In the Designer Cloud® application, you can create and assign roles, each of which consists of one or more privileges. A privilege is a level of access to a type of object, such as flows. 

Below, you can review the available privileges, including the supported levels for each.

For more information on privileges and roles, see Overview of Authorization.

Privileges

Flows

The flows privilege governs access to flow objects. 

Access LevelNameDescription
0noneAssigned role cannot see or use flows, including the pages where flows are available.
1viewer

Assigned user can access Flows page and Flow View page for flows that the user owns or has been shared. User can also run jobs on the user's own flows.

User cannot make changes to any flows.

2editor

All of the above, plus:

Assigned user can edit, share, and run jobs on flows to which the user has access.

NOTE: By default, editors can also schedule flows. This option can be disabled by an administrator.

3author

All of the above, plus:

Assigned user can create new flows, schedule flows, and delete flows.

Connections

Feature Availability: This feature may not be available in all product editions. For more information on available features, see Compare Editions.

The connections privilege governs access to connection objects.

Access LevelNameDescription
0noneAssigned role cannot see or use connections, including the pages where connections are available.
1viewer

Assigned user can access Connections page for connections that the user owns or has been shared. User can share connections.

User cannot make changes to any connections.

2editor

All of the above, plus:

Assigned user can edit and share connections to which the user has access.

3author

All of the above, plus:

Assigned user can create new connections and delete connections.

Plans

Feature Availability: This feature may not be available in all product editions. For more information on available features, see Compare Editions.

The plans privilege manages access to plan objects.

Access LevelNameDescription
0noneAssigned role cannot see or use plans, including the pages where plans are available.
1viewer

Assigned user can access Plans page and Plan View page for plans that the user owns or has been shared. User can also run jobs on the user's own plans.

User cannot make changes to any plans.

2editor

All of the above, plus:

Assigned user can edit, share, and run jobs on plans to which the user has access.

NOTE: By default, editors can also schedule plans. This option can be disabled by an administrator.

3author

All of the above, plus:

Assigned user can create new plans, schedule plans, and delete plans.


Standard Roles

The following roles are provided with the product.

NOTE: The following roles cannot be removed.

default

The default role is assigned to each user when the user is initially created. This role contains the following permissions:

PrivilegeAccess Level/Name
Flows3 - author
Connections3 - author
Plans3 - author
User defined functions3 - author

Tip: You can modify the default role if you want to set a lower level of base access for each new user of the product. For more information, see Overview of Authorization.

Workspace admin

This role provides super-user privileges to the assigned user.

NOTE: This role enables for the user owner-level access to all objects in the project or workspace and access to all admin-level settings and configuration pages in the admin console. This role should not be assigned to many users. At least one user should always have this role.

NOTE: You cannot modify or delete this role.

See Also for Privileges and Roles Reference:

Error rendering macro 'contentbylabel'

parameters should not be empty

  • No labels

This page has no comments.