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.
Share 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 |
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 |
|
Read |
Read |
Any stage |
Data permission |
|
N/A |
Write |
Any stage |
Data permission |
|
Read |
Change Data |
Any stage |
Data permission |
|
Read |
Read Data |
Any stage; most applicable to data stores and data views. |
Data permission |
|
Read |
Manage Security |
Any stage |
Functional (UI) permission |
|
Read |
Execute |
Any stage; most applicable to analyses, data views, and process models. |
Functional (UI) permission. |
|
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.