Board Access and Permissions
Who can open a board, who can change it, who can build its forms, and how per-board access differs from the organisation-wide permissions.
The three rights
Tickets are controlled by three separate permissions. Two of them were renamed in this release, so an administrator who remembers the old switch needs the middle column:
| Right | Shown to admins as | Used to be called |
|---|---|---|
Tickets | Tickets | (unchanged) |
Tickets.Boards | Board management | Settings.Boards |
Tickets.Forms | Forms | Automation.Form |
Tickets.Boards and Tickets.Forms sit underneath Tickets, so neither of them does anything on its own — a member needs Tickets as well.
What each one changes on screen
These rights behave differently from most others in Yaplet: instead of letting you click something and then refusing, they hide the thing entirely. If a colleague says a tab is missing, this is why.
Tickets
Grants the Communications → Tickets entry in the sidebar and the board's kanban. It also decides whether the person can actually change anything: moving a card between columns, editing a ticket, archiving it, deleting it and adding a comment all require it. Until this release any signed-in member of the organisation could do all of that through the API without holding the right.
The Tickets entry only appears at all when the person can see at least one board — see per-board access below.
Board management
Adds the ＋ New board row at the bottom of the Tickets list, the board's Settings tab (rename, type, roadmap widgets, delete), and duplicating a board. Without it, a colleague sees the board and its tickets but has no Settings tab.
Forms
Adds the board's Forms tab, where the intake forms that feed the board are built. Without it the Forms tab is not shown — deliberately, because a form built by someone without ticket access could never actually run.
Launching a form into a live conversation from the inbox's Start button does not need this right. That button, and the endpoint behind it, only check that the organisation owns the add-on — so a colleague who cannot see the Forms tab can still start an existing form on a chat.
A rough edge worth knowing
Per-board access
On top of the three rights, access is granted one board at a time. Two colleagues can hold exactly the same Tickets right and still see completely different boards.
Grants are made on the team screen, which is not in the left-hand menu: open the profile menu behind your avatar in the top-right corner, choose Manage team, expand the member's row, and use the Board access switches — one per board the organisation has. (The screen itself is titled Organizations.) Whoever creates a board is granted access to it automatically.
An organisation owner bypasses this entirely and sees every board. An administrator does not — an admin can legitimately be restricted to some boards, which is different from how brand access works, where owners and admins always see everything. The same bypass now applies to a ticket's board picker: an owner with no explicit grants sees every board there, where previously they got an empty picker and could not move a ticket at all.
What you have to be paying for
All three rights come with the Feedback boards & bug tracker add-on ($15/month). Buying it grants Tickets, Board management and Forms together. There is no separate Forms product any more, and none can be bought, even though the add-on's own card mentions only boards and bug tracking.
Action by action
| Action | Right required |
|---|---|
| Open a board and read its tickets | Tickets, plus access to that board |
| Move a card between columns | Tickets |
| Edit, archive or delete a ticket | Tickets |
| Add an internal comment | Tickets |
| Create a board (＋ New board) | Board management |
| Rename a board or change its type | Board management |
| Delete a board | Board management |
| Duplicate a board | Board management |
| Open the Forms tab and build a form | Forms |
| Launch a form from the inbox's Start button | None of your own — only the add-on on the organisation |
Where to go next
For what a board is and where to create one, see Boards. For building the intake forms themselves, see Forms. To grant the rights, see Organizations.