Roles and permissions

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

Role overview

Role	Scope	Who assigns it
Organization Admin	Full org-wide control	First installer; other admins
Team Manager	Manages assigned teams	Organization Admin
Member	Default role for all users	Automatic on join
Check-in Owner	Controls a specific check-in	Organization Admin or Team Manager

Permissions matrix

Permission	Org Admin	Team Manager	Member	Check-in Owner
View own check-in responses	Yes	Yes	Yes	Yes
Respond to check-ins	Yes	Yes	Yes	Yes
Give and receive kudos	Yes	Yes	Yes	Yes
Create check-ins	Yes	Yes	No	No
Edit check-in questions and schedule	Yes	Own teams	No	Assigned check-in only
View team check-in reports	Yes	Own teams	No	Assigned check-in only
Create tables	Yes	Yes	No	No
Create automations	Yes	Yes	No	No
Manage team membership	Yes	Own teams	No	No
Invite members to the organization	Yes	No	No	No
Remove members from the organization	Yes	No	No	No
Change a member’s role	Yes	No	No	No
View and manage billing	Yes	No	No	No
Change organization settings	Yes	No	No	No
Connect or disconnect chat platforms	Yes	No	No	No
Delete the organization	Yes	No	No	No
Set personal timezone and reminder time	Yes	Yes	Yes	Yes
View agent dashboard and Home feed	Yes	Yes	Yes	Yes
Connect a coding agent	Yes	Yes	Yes	No

Edge cases

Note: A person can be both a Team Manager and a Check-in Owner. Permissions stack, so 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.

Related how-tos

• Managing members: adding and removing users
• Creating and managing teams
• Understanding your Dailybot organization