This section provides an overview of sharing principles, limitations, and approaches.
NOTE: You can share connections, too. See Share Connections below.
For more information on how to share a flow or send a copy of it, see Share Flow Dialog.
In the collaborative approach, two or more users can work on the same flow. When a flow is shared, all flow objects are shared, including:
NOTE: A dataset that is created with parameters cannot be modified by a collaborator. It can only be modified by the owner.
- Job results
- Webhook tasks
NOTE: Sharing of data is managed at the flow level. You cannot share individual recipes or datasets from within a flow.
NOTE: You cannot share a flow with yourself.
- The default output directories for any user can be accessed by any other user. This configuration must be managed in the base storage layer.
- When the sample is executed, an individual user must set his or her default output directory to a location that shared users of the flow can access.
When flows are shared with you, you can access them through the Shared with Me tab in the Flows page. In addition to accessing the flow based on your set of permissions, you can also:
Send a copy of the flow to another user
NOTE: If a dataset from a shared flow is referenced in another flow, when sharing access is removed from the flow, the referenced dataset is still available in the other flow.
NOTE: If a flow is unshared with you, you cannot see or access the datasources for any jobs that you have already run on the flow. You can still access the job results. This is a known issue.
As needed, you can send a copy of a flow to one or more users. Each user with whom you send the flow has an independent version of the flow. Changes made in copies of flows do not affect the original flow, and vice-versa. Examples:
- Output objects are not included in the shared copy.
- Reference datasets are not included in the shared copy.
- Webhook tasks Webhook tasks are not included in the shared copy.
When you create a copy, you can optionally create copies of the imported datasets with the copied flow. Implications:
|Did not copy imported datasets||Did copy imported datasets|
When you open your flow, you must swap in imported datasets to replace any missing or inaccessible ones. See Flow View Page.
|Copied flow contains independent imported dataset objects|
When a flow containing parameters is copied, any changes to parameter values in the copied flow also affect parameters in the original flow. As a workaround, you can export and import the flow into the same system and replace the datasets in the imported flow.
|Parameter values in the flow copy are set independently.|
The users to whom copies are sent are owners of those copies. They have full permissions over the flow and its datasets.