Skip to main content

Which roles can be defined in the User Management?

Abstract

Which roles can be defined in the User Management?

There are seven roles PoolParty SuperAdmins can assign to users in the system:

  • PoolPartyReadOnly

    This role allows logging in to PoolParty and open projects with read-only access.

  • PoolPartyUser

    This is the default user role in PoolParty allowing users to log in to PoolParty and open and edit projects.

  • PoolPartyAdmin

    This role allows you in addition to the PoolPartyUser role to create and delete projects for the assigned groups and gives users access to the Advanced menu, where several advanced configuration functions are available. Also, you need the PoolPartyAdmin role to access the Ontology Management and create and edit ontologies and custom schemes.

  • PoolPartySuperAdmin

    This role allows you in addition to the PoolPartyAdmin role access to the User Management and the Snapshot Dashboard.

  • WikiEditor

    This role allows only access to the Wiki frontend of a project. Users with this role cannot log in to PoolParty.

  • ApiUser

    This user role allows read and write access to the PoolParty API. Users with this role cannot log in to PoolParty.

  • ApiAdmin

    In addition to the rights ApiUsers have, users with this role can for instance create and modify ontologies, delete and create projects and create, delete and restore snapshots. Users with this role cannot log in to PoolParty.

In addition to those roles, use role None exists in PoolParty. Depending on configuration, this role might get automatically assigned to users managed by an LDAP IDP. Users with this role cannot use PoolParty.

For a detailed description of the individual permissions associated with these roles, refer to User Roles - Server Permissions and User Roles - Project Permissions.