In Data Pipelines, all resources, such as pipelines, data connections or schedules belong to your organization. This enables collaboration among users within the same organization.
Example scenario: User A registers for a new Data Pipelines account. At the time of registration a new Data Pipelines organization is created of which User A becomes the Org Admin. User A then proceeds to connect some data sources, create a pipeline and schedule it.
User A sends an invite to User B who then signs up for a Data Pipelines account via the invite link. User B now also belongs to User A's organization and has the User role. User B will not be able to invite subsequent users as only Org Admin can do that but User B will now be able to see and access all of the pipelines and other resources created by User A. User B can also create pipelines and connect data which will be accessible by User A.
There can be multiple Org Admins within an organization in which case they will all be able to invite subsequent users and update existing users.
When User A leaves the organization, their account is deleted. Because all of the resources User A has created belongs to their organization, none of the pipelines or other resources will be affected. Schedules will continue running unaffected. User B will not automatically become Org Admin when User A's account is deleted so User A should make sure they set another user's role to Org Admin.
The following resources are shared within organizations:
- data pipelines
- data connections
Sharing resources between organizations is not currently supported. It is, however, easy to share pipeline definitions in JSON format. Data connections will have to be set up manually as the connection parameters are not part of the pipeline definition.
Read our tutorial on how to add a new user to your organization.