Introduction to the user roles in DailyBot

DailyBot integrates different roles for the users and we recommend administrators to read about their scope and impact.

Administrator

This is the most powerful role that allows users to add/remove other users, add/remove teams, and even ask for deletion of the organization.

You can have as many administrators as you want and you can manage these permissions in the Organization settings, at the Members section.

Teams manager

This is a special permission that gives users the super powers to create/delete and change teams, they can invite/remove members from any team and see data related to all teams across the different Skills.

You can also have as many team managers as you'd like, and you can manage these permissions in the Organization settings page, at the Members section.

Team administrator

This is a special role for a user (usually a member) that needs to manage a specific team.

You can as many team administrators per team as you need. You can manage these permissions in the Teams settings, and then opening the members window for the specific team.

Member

This is the default permission for any new user that gets invited or joins your organization. Members can interact with Skills, their profile, but cannot manage teams or the organization. Members can only see and operate on the teams they are members of.

Owner

While not a user role in itself, this is assigned by default to any new user that creates a new check-in. A check-in owner cannot transfer the ownership of said report, but it can invite other members to be administrators if they need a level of independence when operating it.

Editor

This is not a user role per se either, and it can be assigned to any user that needs to manage a specific check-in. There can be many editors in said report and the user with this permissions cannot invite other editors, nor remove these permissions from other users.