Depending on the level of access and control you need in Hive, there are five distinct User Permission Roles to choose from.
This article provides an overview of each and what you can expect as a user with that specific permission level. If you'd like to learn more about who in your workspace has what role, or to change user permissions, read more here.
This user has limited access only to specific projects they've been added to by a member, admin or system admin of the respective workspace. They cannot change project settings. | |
Member | This user makes up the majority of users in Hive and has access to projects they were invited to or created themselves, as well as full app functionality. They have the ability to change project settings. |
Admin | This user has access to everything Members have as well as control over Workspace Settings. |
System Admin | This user has access to everything Admins have as well as access to all projects in the workspace, including the ability to self-add to projects, delete any projects and full workspace settings control. |
Restricted User | Restricted Users can collaborate on projects and actions while having limited access to workspace administration and selected Hive apps. This role is useful for team members who need to contribute to work without having full Member permissions. By default, Restricted Users can create and update actions, comment, track time, and work within projects they can access. They cannot manage workspace settings, billing, users, or Enterprise Security, and they cannot delete or archive projects. Restricted User permissions are configurable by workspace admins in Enterprise Security > User Permissions. Available apps and actions may vary based on the workspace’s settings and the user’s assigned permissions. Note: The Restricted User role is available through the Enterprise Security app. Workspace admins can configure Restricted User permissions under Enterprise Security > User Permissions. |
Configure restricted members
With Enterprise Security enabled, a workspace admin can open Settings → Enterprise Security → User Permissions and find Restricted members.
Turn on Enable restricted member type.
Optionally enable Add new users as restricted members by default. This sets the default for newly added internal members; it does not change existing users’ roles. An explicitly selected invite role overrides this default.
Use Show permissions for to choose Actions, Projects, General, or Apps, then adjust the available permissions.
Under Projects, separate controls let you allow restricted members to edit project start and end dates, edit project custom field values, and create, rename, or delete project baselines. These controls do not grant access to projects the user cannot otherwise access.
To change an existing user’s role, open Manage users.