Setting column permissions

If you are a main manager for a project, you can set the permissions for some columns. Permissions can be set for all custom columns as well as the Product backlog priority and Sprint priority columns.

If access to one of the priority columns is revoked for a user, that user will no longer be able to change the priority of items.

Custom column permissions primarily affect the Product Backlog and Planning sections. For more information on how to configure detailed access permissions in the Quality Assurance section, see Setting Quality Assurance permissions.

Custom column permissions do not apply to main managers.

1. Click More in the Product Backlog or Planning view and choose Customise project.

The Customise project dialog box opens.

2. Select the Column permissions tab.

The tab is split into two sections; the left contains all custom columns in the project, and the right shows the permissions added to the currently selected column.

3. Use the Base Permission drop-down menu to select the default permission for each column, which will be applied to all users and groups unless an override permission is specified. The following options are available:

  • Edit - The user can edit the column without any restrictions. This applies even for Helix Plan items that the user normally cannot edit. For example, this can be useful if you want certain users to be able to edit specific fields in tasks outside their scope without making them main manager.
  • Normal - The user can only edit this column in Helix Plan items to which they have been delegated or assigned, or items in sprints where they are a member if they have been given access. For more information, refer to Involving team members.
  • Read-only - The user can view but not edit the column. This option overrides delegated rows.
  • Hidden - The column will not be visible to the user at all. If the column occurs in multiple projects, it will only be hidden in the project where this permission is applied.
    • When a dashboard is shared, it may reveal data in hidden columns if the dashboard owner can view the data. Function columns can also reveal data in hidden columns.
    Only the Hidden permission applies to columns in the Quality assurance section. For more information on how to configure detailed access permissions in this section, see Setting Quality Assurance permissions.

4. To create a Permission Override, start by selecting a custom column in the left list.

An override permission will always take precedence over the base permission, even if the base permission is more restrictive.

5. Click Add User or Group.

A menu containing a list of all users and user groups in the project—except main managers—will appear in the project. Beneath the list is a search field and filter option, enabling you to find specific users or groups quickly.

6. Select one or more users/groups from the list and click Ok.

The selected users and groups will be added to the list on the right.

7. Click the Permission Override drop-down menu next to the user or group, and select which permission to apply. The options match those available when selecting the base permission.

If more than one override permission is applied to the same user, the most restrictive will always take precedence. For example, if they are part of two different groups with the permissions Read-only and Hidden respectively, the latter option will apply and the column will not be visible.

8. Click OK to save the changes.