Skip to main content

Managing access to Datasets in an organization

Updated over a week ago

This feature is available to Organization Administrators

When exploring the available Datasets, use the Shared With and Shared With Teams options to control which users can view and use the organization's Datasets.

Shared with

On a Dataset's row, click on the drop down in the Shared With column to control whether a dataset is shared with:

  • users in the organization and external accessors,

  • organization users only, or

  • admins only.

Datasets that have been shared with Admins only or Organization can be extended to specific teams.

Shared with teams

Click on the existing selection under Shared With Teams to share a dataset with one or more Teams of users in the organization:

Teams and User Roles are a flexible feature of Neara that make it easier to manage and configure settings and permissions for groups of users.

Contact your Customer Success Manager for more information about accessing this capability.

Select an access level for that Dataset:

  • Read allows users to access and add a dataset to a project.

  • Annotate allows a user to annotate the dataset for existing annotation layers additionally.

  • Write allows a user to rename a dataset, and create new annotation layers. If the user also has the general permission to process datasets, they will also be able to process this given dataset.

  • Admin allows a user to delete a dataset additionally.

Permissions for users with multiple team membership

Access Levels for Shared With Teams are hierarchal. Whichever option provides more access in a Team "wins".

As an example, if a user is a member of two (2) Teams, and a Dataset is shared with both of those Teams, the user will gain the highest permission from either Team e.g.

they can rename the Dataset if one Team is given Write access level, and can delete the Dataset if the other Team is given Admin access level.

Renaming a Dataset does not alter access levels

Team Sharing permissions are based on the Dataset's unique ID, and renaming a Dataset does not modify its ID.

Regenerating a Dataset may alter access levels

If a Dataset is generated or re-generated in an automated Neara Pipeline, it may produce a new Dataset (as opposed to updating an existing one) with a new ID.

Previous Team Sharing access levels will not propagate to the new Dataset in this case.

Did this answer your question?