Teams and access
Roles and permissions
Understand Owner, Admin, and Member roles for teams and projects.
Clankee uses roles at two levels: team and project. Workspace member roles map Discord users to Clankee users. Integration accounts can also be Team or Private.
Team roles
Assignable invite roles in the UI are Admin and Member. The person who creates the team is Owner.
| Capability | Owner | Admin | Member |
|---|---|---|---|
| Update team | Yes | Yes | No |
| Delete team (non-personal) | Yes | No | No |
| Add / update / remove members | Yes | No | No |
| Create invitations | Yes | Yes | No |
| Cancel invitations | Yes | Yes | No |
| Open Team Settings | Yes | Yes | No |
Important team rules
- Personal teams cannot be deleted.
- The team Owner cannot be removed.
- Admins can invite people, but only Owners can change or remove existing members.
Project roles
| Capability | Owner | Admin | Member |
|---|---|---|---|
| View and use the project | Yes | Yes | Yes |
| Update project settings | Yes | Yes | No |
| Delete project | Yes | No | No |
| Add / update / remove project members | Yes | Yes | No |
| Open Brain | Yes | Yes | No |
| Create and manage workspaces | Yes | Yes | No |
| Add knowledge base notes | Yes | Yes | Yes |
Project members must already be on the team. You add them from available team members in project settings.
Workspace member roles
On a Discord workspace, members can be labeled Member or Admin. Use this to link Discord users to Clankee users. Managing workspace members still requires project update permission (Owner or Admin on the project).
Integration visibility
| Access | Who can use the connected account |
|---|---|
| Team | Shared in the project/team context |
| Private | Limited to allowed project members (plus people who can update the project) |
Who cannot do what (common cases)
- Project Members cannot open Brain, edit project settings, or connect new workspaces.
- Team Members cannot open Team Settings or send invitations.
- Team Admins cannot remove members or change member roles.
Tips
- Make at least one backup Owner/Admin for shared teams so invites and settings are not blocked.
- Use Private integrations for personal credentials; use Team for shared company accounts.