Sharing¶
You can share a variety of assets within your organization, including Use Cases, datasets, applications, and models. You may want to do this, for example, to get the assistance of an in-house data scientist who has offered to help optimize your data and models. Or, perhaps a colleague in a different group would benefit from your model's predictions.
When you share an asset with a user, group, or organization, DataRobot assigns the default role of User or Editor to each selected target (See Roles and permissions for more information).
Note the following when sharing or removing access:
- Not all entities allow sharing beyond a specific user.
- You can only share with active accounts.
- You can only share up to your own access level (a consumer cannot grant an editor role) and you cannot downgrade the access of a collaborator with a higher access level than your own.
- Every entity must have at least one owner (entity creator by default). To remove the creator, that user must assign the owner role to one or more additional collaborators and then remove themselves.
- Data connection and data asset entities must have at least one user who can share (based on the “Allow sharing” setting).
Note
You can also share custom models and environments as part of the MLOps workflow.
Share assets¶
To increase collaboration, you can share assets with other DataRobot users, groups within your org, and with the entire organization. However, note that it is required that users and groups must belong to the same organization when sharing. See tenant isolation and collaboration for details.
The share modal functionality is largely the same across DataRobot, however, there can be minor variations depending on the asset type. Variations can include external sharing, the ability to add a note and/or send a notification, different sharing roles, and more. See below for examples:
When adding team members to a Use Case, you can only add users and/or organizations.
When sharing a custom application, you can enable an external sharing link and optionally, send a notification and/or add a note.
When sharing a deployment from Console, you can choose from the following roles: Owner, User, Consumer. The User role replaces the more commonly seen Editor role.
If you encounter an error, review the data asset roles.
Share dialog modal¶
The fields of the Share dialog differ slightly. Generally:
| Field | Description |
|---|---|
| Share with | Identifies the recipient(s). This can be any combination of user email, group, or organization (if supported). |
| Role | Specifies recipient access level to the asset. You can grant access at the same or a lower level than your own access. |
| Shared with | Lists the recipients and their assigned roles (and, for dataset, additional privileges). Use the dropdown to change the role, click the x to remove a recipient. |
| Allow sharing | Provides the recipient with permission to re-share the asset with others (up to their level of access). |
| Can use data | Allows the recipient to use the dataset for certain operations (e.g., download data, create project from dataset). |
| Add note | Allows you to add a note that to be included in the notification sent to the recipient. |
More info¶
Share dialog quick reference
Recipients can be:
- User: Any individual in your organization.
- Group: A selection of users, assigned by your admin, to which permissions are applied in bulk.
- Organization: A larger collection of users, also configured by the admin.
Role selections are dependent on the access type and can be:
- Owner (read/write/administer)
- Editor or User (read/write)
- Observer or Consumer (read-only)
How is the recipient alerted?
When sharing is successful, DataRobot sends the recipient(s) a notification email containing a link to the shared asset. Once clicked, the asset (or a log in prompt) opens in DataRobot.
Additionally, DataRobot sends an alert to the recipients Notification center. Click the notification icon (
) for details.
Why can't I share my asset?
If you get an error when you try to share, it may be because:
- Your recipient is not a DataRobot user or is a user but is outside your DataRobot organization.
- There is a problem with roles and/or permissions. Both your role and access level and the recipient's role influence whether and how you can share an asset with that user or group of users.
Effect of your role and access level
When assigning roles, you can assign the same, or a lower, access level as your own. For example, if you have User (read/write) access to a project, you can grant another user User or Consumer (read-only) access, but you cannot grant them Owner (read/write/administer) access.
Effect of the recipient's role and access level
The share recipient's access to DataRobot assets is controlled by role-based access control (RBAC) roles, assigned by the organization's DataRobot administrator. Those designated privileges override your assignments. If you attempt to share an asset at a role above the user's RBAC privileges, sharing is prevented. Try assigning a more restrictive role.
The following provides additional documentation related to sharing.