Roles and permissions: the complete reference
This reference lists Dailybot’s roles and a full permission matrix so admins and team leads know exactly who can perform each action.
Permissions matrix
| Permission | Org Admin | Team Manager | Member | Check-in Owner |
|---|---|---|---|---|
| View and submit own check-in responses | Yes | Yes | Yes | Yes |
| View Home feed and agent dashboard | Yes | Yes | Yes | Yes |
| Give and receive kudos | Yes | Yes | Yes | Yes |
| Set personal timezone, reminders, notification prefs | Yes | Yes | Yes | Yes |
| Connect a personal coding agent (where enabled) | Yes | Yes | Yes | No |
| Create new check-ins | Yes | Yes | No | No |
| Edit check-in questions, schedule, and targets | Yes | Own teams | No | Assigned check-in only |
| View aggregated check-in reports | Yes | Own teams | No | Assigned check-in only |
| Create and edit tables | Yes | Yes | No | No |
| Create and edit automations | Yes | Yes | No | No |
| Manage membership for assigned teams | Yes | Own teams | No | No |
| Invite users to the organization | Yes | No | No | No |
| Remove users from the organization | Yes | No | No | No |
| Change any member’s org role | Yes | No | No | No |
| View and manage billing and invoices | Yes | No | No | No |
| Update org-wide settings (name, logo, policies) | Yes | No | No | No |
| Connect, reconnect, or disconnect chat integrations | Yes | No | No | No |
| Configure org security options (SSO, session policy where offered) | Yes | No | No | No |
| Access audit or export tools (plan-dependent) | Yes | No | No | No |
| Delete the organization | Yes | No | No | No |
Edge cases
Note: Check-in Owner applies per check-in. A member with that assignment can edit that workflow’s questions and view its reports without being a Team Manager.
Note: Team Manager scope is limited to teams they manage. “Own teams” in the matrix means teams on their manager list, not the entire org.
Note: The first installer of Dailybot in an org is typically an Organization Admin. At least one Organization Admin should always remain; transfer admin before removing yourself.
Note: Features such as API keys, webhooks, or enterprise SSO may appear only on certain plans — the role still gates access when the feature is enabled.