Hi,
First of all, thank you for the great work on Quackback. I believe the quality of every aspect of this project is just purely excellent and it is an undiscovered gem.
I have been reviewing the documentation around board visibility and roles/permissions, and I wanted to ask whether more granular board access control is currently possible or planned for the project.
From what I understand, board visibility is currently binary:
- Public: anyone can view the board on the portal, while signed-in users can vote, comment, and submit.
- Private: only team members, meaning Members and Admins, can view the board.
It looks like there is currently no board-level access control for specific portal users, customer segments, user groups, or a subset of team members. Roles also appear to be workspace-wide, and the roles/permissions matrix does not seem to include board-scoped permissions.
The use case I have in mind is being able to restrict access not only at the board level, but ideally also with more granular permissions inside a board. For example:
- A board visible only to selected customers
- A board visible only to users belonging to a certain segment, organization, tenant, or customer account
- A board visible only to a subset of internal team members
- Multiple private boards with different audiences
- Individual posts, tasks, feedback items, or roadmap entries inside a board visible only to specific users, customer groups, organizations, or internal teams
- The ability to expose some tasks within a board publicly while keeping other tasks private or restricted
- The ability to allow certain users to view a board but only see tasks that are relevant to their organization, segment, or assigned permissions
- Task-level permissions for actions such as viewing, commenting, voting, submitting, editing, or receiving updates
- Internal-only tasks within an otherwise customer-facing board
- Customer-specific tasks within a shared board, where each customer only sees the items relevant to them
- Role- or group-based task visibility, so different audiences can collaborate in the same board without exposing unrelated or sensitive items
This would be very useful for cases where different customer groups, internal teams, tenants, or product areas need to collaborate in the same feedback space, while still keeping sensitive or customer-specific items properly separated.
Could you please confirm whether this kind of granular board visibility is already supported in some way that I may have missed?
If not, is this something that is already planned or would be considered for the roadmap?
Thanks again for your work on the project.
Hi,
First of all, thank you for the great work on Quackback. I believe the quality of every aspect of this project is just purely excellent and it is an undiscovered gem.
I have been reviewing the documentation around board visibility and roles/permissions, and I wanted to ask whether more granular board access control is currently possible or planned for the project.
From what I understand, board visibility is currently binary:
It looks like there is currently no board-level access control for specific portal users, customer segments, user groups, or a subset of team members. Roles also appear to be workspace-wide, and the roles/permissions matrix does not seem to include board-scoped permissions.
The use case I have in mind is being able to restrict access not only at the board level, but ideally also with more granular permissions inside a board. For example:
This would be very useful for cases where different customer groups, internal teams, tenants, or product areas need to collaborate in the same feedback space, while still keeping sensitive or customer-specific items properly separated.
Could you please confirm whether this kind of granular board visibility is already supported in some way that I may have missed?
If not, is this something that is already planned or would be considered for the roadmap?
Thanks again for your work on the project.