Permissions
Bnder permissions control what users and teams can view or change in the app, API, and connected integrations. Manage workspace access from Settings → People and project-specific access from the project's Settings area.
How does it work?
The app first checks whether the user is the workspace owner. If not, it checks what permissions have been granted to the user directly and to their Bnder teams. If any of their teams have the permission, they will be able to execute the command that requires that permission. Membership inherited from child teams also counts, so a permission granted to a parent team applies to members, leads, and managers of the child teams underneath it.
Example
The user is in Team A and Team B. Team A has been granted the MANAGE_TASKS and MANAGE_PROJECTS permissions. Team B has only been granted the SET_STATE permission and no others. Because the user is in both teams, they can create tasks, set tasks state and create projects.
Grant permissions
- Open Settings → People.
- Select Users or Teams.
- Open the user or team whose access should change.
- Add the required permission or apply a preset.
Changes apply immediately to the app and connected integrations.
Revoke permissions
Open the same user or team in Settings → People and remove the permission.
Even after revoking a user's direct permissions, they may still have access to certain commands through teams that provide the same permissions.
Project based permissions
Project permissions limit access to one project. Open the project, choose Settings, then manage its Users or Teams. Grant only the access needed for that project; workspace permissions continue to apply globally.
Permission presets
Permission presets are an easy way to grant a user or team multiple permissions at once. They can be used to grant a basic set of permissions to a user or team for a common responsibility in the workspace.
When a preset is applied, all permissions that are already granted to the user or team will be removed and replaced with the permissions of the preset. After applying a preset, more permissions can be granted to the user or team. The permissions granted by the preset can be revoked too.
Apply each preset to either one user or one team at a time. The list command works the same way: list a user to see their effective permissions, including team inheritance, or list a team to see the permissions granted directly to that team.
For large workspaces, Member Approval can keep internal assignment pickers focused on approved staff while permissions continue to control what each member can view or change.
Available presets
| Preset name | Permissions granted |
|---|---|
| admin | Includes every permission available |
| contributor | - MANAGE_TOPICS - MANAGE_DOCUMENTS - READ_DOCUMENTS - MANAGE_TASKS - VIEW_TASKS - SET_STATE - MANAGE_MILESTONES |
| guest | - VIEW_TASKS - READ_DOCUMENTS |
All permissions
| Bot | Permission | Use case |
|---|---|---|
| Task Manager | VIEW_TASKS | Is required to view projects, their tasks, and milestones |
| Task Manager | SET_STATE | Is required to update the state (todo, in progress, done) of a task. |
| Task Manager | MANAGE_TASKS | Is required to create, delete, edit, assign, unassign and restore a task. |
| Task Manager | MANAGE_TICKETS | Is required to open ticket areas and manage ticket list, details, settings, templates and related public ticket setup. |
| Task Manager | MANAGE_MILESTONES | Required to create, edit or delete milestones |
| Knowledge Manager | READ_DOCUMENTS | Is required to read a document and list all documents and viewing projects |
| Knowledge Manager | MANAGE_DOCUMENTS | Is required if a user needs to create, edit, change the topic, delete and restore a document. |
| Knowledge Manager | MANAGE_TOPICS | Is required to create, rename, delete and restore a topic and all of its documents. |
| Task Manager, Knowledge Manager | MANAGE_PROJECTS | Is required to create, rename, delete and restore projects. |
| Calendar Manager | CREATE_EVENTS | Is required to create a new event. |
| Task Manager, Calendar Manager, Knowledge Manager | MANAGE_PERMISSIONS | Is required to show all permissions, grant or revoke permissions |
| Task Manager, Calendar Manager, Knowledge Manager | MANAGE_SETTINGS | Required to change settings by the /settings command |
Task comments and their attachments follow the parent project's VIEW_TASKS permission. If that permission is removed, members can no longer upload or delete attachments on their earlier comments.
Project lists hide projects without VIEW_TASKS. Project details and milestone names or due dates are unavailable without that permission on the parent project.
Moving a document between projects requires permission to manage documents in both its current project and destination project. If either permission is missing, Bnder leaves the document unchanged.
Discord permission commands
Discord-connected workspaces can also grant, revoke, list, and apply permission presets from the integration. Discord server owners and members with Discord Administrator access bypass Discord command permission checks, while Bnder app and project access still follows the workspace permission model.
See the Discord command reference for the complete option list.
Grant a permission
Revoke a permission
List all permissions
Apply a preset