Skip to content
Reference Admin team-manager Member check-in-owner

Roles and permissions: the complete reference

Roles and permissions: the complete reference

Dailybot has four roles that control what each person can do. This reference covers all of them.

Role overview

RoleScopeWho assigns it
Organization AdminFull org-wide controlFirst installer; other admins
Team ManagerManages assigned teamsOrganization Admin
MemberDefault role for all usersAutomatic on join
Check-in OwnerControls a specific check-inOrganization Admin or Team Manager

Permissions matrix

PermissionOrg AdminTeam ManagerMemberCheck-in Owner
View own check-in responsesYesYesYesYes
Respond to check-insYesYesYesYes
Give and receive kudosYesYesYesYes
Create check-insYesYesNoNo
Edit check-in questions and scheduleYesOwn teamsNoAssigned check-in only
View team check-in reportsYesOwn teamsNoAssigned check-in only
Create tablesYesYesNoNo
Create automationsYesYesNoNo
Manage team membershipYesOwn teamsNoNo
Invite members to the organizationYesNoNoNo
Remove members from the organizationYesNoNoNo
Change a member’s roleYesNoNoNo
View and manage billingYesNoNoNo
Change organization settingsYesNoNoNo
Connect or disconnect chat platformsYesNoNoNo
Delete the organizationYesNoNoNo
Set personal timezone and reminder timeYesYesYesYes
View agent dashboard and Home feedYesYesYesYes
Connect a coding agentYesYesYesNo

Edge cases

Note: A person can be both a Team Manager and a Check-in Owner. Permissions stack — they get the union of both roles’ capabilities.

Note: The first person to install Dailybot on a chat platform automatically becomes an Organization Admin. There must always be at least one Organization Admin in every organization.

Note: Check-in Owner is scoped to a specific check-in, not the entire org. Someone can own one check-in while having no special permissions on others.