There's some nuance in how DailyBot manages your organization's data.

To protect everyone's right to privacy, as well as empower managers to do their best work, and keep teamwork transparent, we adopted the current approach to both roles and permissions in DailyBot. Keep reading to learn more.

(Users with different roles as participants in the same check-in)

1️⃣ Roles

You can think of user roles as a pre-packaged set of permissions for someone in your organization. Currently, there are three different roles in DailyBot, each one with its own set of expectations and responsibilities for the users that take it on.

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. Now, they can also manage their own check-ins and forms.

2️⃣ Permissions

A permission consists of any individual configuration that a user can take on to control the behavior of a feature beyond their regular capabilities. 

Owner

This is assigned by default to any new user that creates a new check-in. A check-in owner can transfer the ownership of the check-in, and it can also invite other members to be administrators if they need a certain level of independence when operating it.

Editor

This can be assigned to any user that needs to manage a specific check-in. There can be many editors in the report and the user with these permissions cannot invite other editors, nor remove these permissions from other users.