Sharing data stages - Data360_DQ+ - Latest

Data360 DQ+ Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
Latest
Language
English
Product name
Data360 DQ+
Title
Data360 DQ+ Help
Copyright
2024
First publish date
2016
ft:lastEdition
2024-07-09
ft:lastPublication
2024-07-09T15:09:58.774265

After creating and saving a data stage, you can share it with other users. Depending on where the data stage is saved and your user permissions, the process of sharing will vary.

Sharing in pipelines

In most cases, the delegation of rights to data stages will be managed solely by your administrator - meaning that once something has been created, the proper group of users will have access to it.

In some cases, however, you the user may be given administer permissions to certain data stages. In these cases, you will need a basic understanding of permissions, which are covered below. For a more detailed treatment of permissions, see Pipelines.

Who to share with: Environment groups

If you've been given administer rights to a data stage, you'll have the ability to grant permissions to environment groups. Environment groups are simply groups of users to which you can collectively delegate access rights.

Environment groups should have meaningful names, so you should be able to figure out which users belong to which environment groups. If this is not the case, you will need to contact your administrator to find out which users are in which environment groups.

How to grant permissions

When sharing a Data Stage, the following permissions can be applied, by right-clicking the data stage, selecting Edit Settings, and then entering the Security tab. The listed permissions can then be granted to environment groups.

Pipeline permission/action matrix

Permission

Can be applied to:

Type

Allows

Implies

Administer

Any stage

Data permission

  • Access to the stage
  • The right to grant stage access to other environment groups.
  • The right schedule data stage execution.
  • The right to view data store load events in the Executions History.

 

Note: A user with Administer permissions to a data stage is different than a Data360 DQ+ administrator.

Read

Create [Stage]

Pipeline, Path

Functional (UI) permission

  • The right to create the selected stage.
  • Must be combined with Write to Save the data stage.

 

  • Users will need Read Data to a data store to Create Analysis or Create Data View.
  • Users will need Read Data to a data view to Create Dashboard.

Read

Read

Any stage

Data permission

  • The right to view the selected stage.

N/A

Write

Any stage

Data permission

  • The right to make and save changes to or within the selected stage.
  • The right to create paths.

 

  • If applied without Create, will grant the right to modify existing stages.

Read

Change Data

Any stage

Data permission

  • The right to Upload Files to Data Stores.
  • The right to Delete all Data from Data Stores and Data Views.
  • Required for case worker to work case store.
  • Required to modify records in Data Entry.

Read

Read Data

Any stage; most applicable to data stores and data views.

Data permission

  • The right to download data store contents.
  • The right to use data store contents in an analysis or data view, when applied to a data store.
  • The right to see data view contents in a dashboard, when applied to a data view.
  • Required for case worker to work case store.
  • Required to view records in Data Entry.

Read

Manage Security

Any stage

Functional (UI) permission

  • The right to delegate permissions to a data stage to other users.

Read

Execute

Any stage;

most applicable to

analyses, data views, and process models.

Functional (UI) permission.

  • The right to Run or Rebuild executable data stages.
  • The right to view an executable data stage's executions history.

Read

Permissions applied at multiple levels - example

Within pipeline A, there are three paths, and permissions have been assigned to three different environment groups:

  • Path A - Only "Environment group A" has access to this path. Users in Environment group A have the following permissions: Create [all data stages], Administer, Change Data, Read Data, Execute and Write.
  • Path B - "Environment group B" and "Environment group C" both have access to this path, but their permissions differ, as follows. Users in Environment group B have the following permissions: Create Dashboard, Read Data and Write. Users in Environment group C have the a more limited set of permissions, as follows: Read Data and Read.
  • Path C - Only administrators have access to this path.

Notes

Within an environment, permissions can be assigned at the pipeline, path, or individual data stage level.

Your organization is likely operating within multiple environments, pipelines and paths. You may or may not have access to all of them, so there are likely things operating behind the scenes that you do not know about.

See also Pipeline permissions and actions.