Issue boards ACL

Access Control Levels on Issue Boards

Julien Benoit avatar
Written by Julien Benoit
Updated over a week ago

Members with full access to an issue board will be able to find the access control of an issue board by clicking on edit access in the access control menu on the issue board settings page.

The edit access control dialogue can look something like this:

This article contains information about the following topics:

Issue board information

Here the name and the owner of the issue board are displayed

Extensions - Close issues

This lets you limit who can close and reopen issues.

When you enable this feature you will see a close issues column appear next to the access column.

Define access for

Here you will be able to specify who has what access to this issue board.

By clicking on the "Member or team" dropdown you will be able to define access for member(s) or team(s).

Once you have selected a member or team they will appear in the list below.

Role column

In the role column the different roles of the projects are described


Default - Full access

Members that are administrators always have full access.

The project owner is an administrator.


Default - Write access

Access given to individual members always overrides access given to teams, all users and owners.

All users

Default - write access

All users is the term used for members that have not gotten specific access as user, team or issue board owner.


Default - Write access

Access given to teams is set for all the teams members unless the member has specific access as a user or an issue board owner.

Issue board Owner

Default - Full access

When you create content in Catenda you become the owner of that content. Owner settings applies to the owner of the content.

Note: Users will be granted the highest permission of what being set in all users, owners and team.

Example: You may use team, or owners to grant users more permission than all users, but not to give them less permission.

The reason behind this is to prevent users to grant themselves more access by removing themselves from a team, or as an owner.

Access column

In the access column you can give the member or team the following access:

No access

Members with no access will not be able to access the issue board.


Members with read access have access to the issue board, but cannot create issues or make comments on existing issues.


Members with write access will be able to do the same as members with read access.

Members with write access will also be able to create new issues and comment on existing issues.

Full access

Members with full access will be able to do the same as members with read and write access.

With full access members will also be able to edit the access settings of this issue board.

Members with full access will be able to add and modify custom fields on this issue board.

Administrators always have full access.

Members with full access will not be able to edit administrator access.

Close issues column

The checkboxes in this column will decide whether these users will be allowed to close issues or not.

At the bottom of the list an issue creator option will also appear.

The issue creator item allows you to give extra permissions to the creator of an issue.
This rule only applies when the issue creator is not listed under "Users" and has write access.

If close issues has been enabled users without this option will no longer be able to:

  • Create closed issues

  • Close existing issues

  • Change the status of an issue that is closed

Save button

Note: Remember to press the save button and reload after you are done to see the changes.

Configured example

This is what the access control dialogue can look like after it has been configured:

Did this answer your question?