Notifications, Glossary, Tips and Tricks

Notifications

Three notification types are available for the functionalities linked to My Team:

• Manager request not accepted. Triggers when a user does not accept a manager's request to confirm their association.
• Team member added to a team. Triggers when a user accepts a manager request to confirm their association or identifies a manager as their manager (when the Automatic Notification for Team Members option is enabled), and when an Admin or Power User creates or forces an association from the Manage Team Requests page.
• Admin asks you to check your team. Triggers when an Admin or a Power User selects the Send notification to a Manager option from the Manage Team Requests page when the association request is in Pending status, to inform the manager that the team member has not accepted the request yet.

Please note that these notifications will not be sent to users in pending, expired or deactivated status, nor to users not having confirmed their association with their manager. When this notification is sent as a mass action to more than 99 users, a background job will automatically start. Learn more on notifications.

Glossary

Here follows a short glossary for the most commonly used terms in this article.

• Managers. A manager is a user (any level of user in the platform) with assigned team members.
• Team Members. The people are managed by a manager. The team members associated with the same manager compose a team, and can thus be called Team Members.
• Association. An association is a working relationship between a manager and the team members composing their team.
• Relationship. The relationship has the same meaning as an association in this article.
• Manager Types. Docebo allows you to define different manager types, that you can associate with managers in order to differentiate them if needed by your organizational chart

Tips and Tricks

If you are importing users and managers via CSV file (manually or in the Automation App), remember that a manager must be always included before any team members refer to him or her, otherwise the system won't be able to establish the relationship. In order to avoid this problem, you can split the user list into two separate CSV files. The first one will contain managers (at least their usernames and the "Is a Manager" field), and the second one will contain user fields and manager association (the "Type of Manager" field). This will prevent any errors during the import, in case a manager hasn't been created yet but a user has been associated with that manager.