Skip to main content

User Management, Rights and Roles

Setup and configure access to the workspace, projects and maps

Written by Oliver Schallehn
Updated over 5 months ago

The platform strives to optimize online collaboration while transferring and managing your marine data. This means that many users with various backgrounds, organizations and permissions need to access those parts of your workspace, projects and data that are needed to collaborate.

In order to provide customized access, (external) users can be invited to the platform and assigned access and permissions to those parts you deem necessary, while providing restrictions to others.

User Management in a nutshell

  • Users can be invited to the platform by providing the invitee’s email address.

  • An invitee has, as soon as user has been activated via the invitation link, a predefined role

  • The roles can be ‘Workspace Administrator’, ’Workspace Member’, ’Guest’

  • Each role has different access and permissions (as further explained below)

  • The Workspace administrator can manage users on the workspace level

  • Project Owners can manage users permissions on a project level

  • Role & Permissions affect:

    • The visibility of projects and files

    • Access to projects and files

    • Availability of certain actions and tools

Inviting users

See Inviting and managing workspace collaborators how to invite new users to the platform.

Roles

The three roles are defined as follows:

  • Administrator

    • Manage users

    • See all and access all projects

    • Can be assigned to one or multiple users

    • Cannot unassign itself from this role to guarantee that there is always another user who can take over this role

  • Member

    • See all projects and access projects when being invited to

    • Can be assigned to one or multiple users

    • Can create projects of which this person becomes a project administrator (see project permissions)

  • Guest

    • Can see and access projects only when being invited to

    • Under full control of workspace administrators or members (when project administrators)

Project Access

(For further project settings see the ‘Project Settings’ article.)

When a project is created (by workspace administrators or members) other users can be invited to this project, see Add/remove a project member for details.

Project Permissions

(For further project settings see the ‘Project Settings’ article.)

Within the project, each user can have an individual set of permissions. These permission are by default grouped according to the user role, but can be customized at will.

Note that both member and workspace administrators can become “Project Admin”

Options are View, All and Custom.

  • All: The user in the project do everything (e.g. upload and share data, rename, move, etc)

  • View: The user can only see all files and their content, but is not allowed to trigger and further activities.

  • Custom: Choose to select from View (enabled by default), Edit, Upload and Share permissions.

File Access

(For further project settings see the ‘Project Settings’ article.)

Access can be set to All or None.

  • All: The user in the project can see and access all files and folders

  • None: When freshly invited but not yet given access to data, Guests can be provided access to data when permitted by other non-guest users.

  • Custom: Custom access can be given to any user. With the users that are administrator or member, full access is provided by default. Guest users are granted no access to folders in a project.
    In order to customize individual folder access for any user, after clicking on the access option 'Custom' behind the name of the user, a modal will appear where the folders can be selected to which access can be granted.

Map Access

(For the description of the entire Map functionality see the ‘Maps’ article.)

All users have got the ability to create their own maps and add layers based on the data access they have. These Maps are initially private.

To collaborate on maps the map creator can invite other platform users to the map.

These users have the possibility to view or edit the map based on the permissions given.

Did this answer your question?