Skip to main content
Question

My Team Manager View - Limit view to direct reports only

  • Nov 10, 2026 6:19 PM UTC
  • 2 replies
  • 6 views

lrnlab
Hero III
Forum|alt.badge.img+10

Hello, in the My Team manager dashboard, does anyone know if there is a way to limit the manager’s view to their direct reports only? No view into their direct report’s team where applicable; essentially limit the hierarchical view to their team only? I’d love to hear your thoughts. Thank you.

2 replies

Moshe.Machlav
Guide I
Forum|alt.badge.img+2

Hi ​@lrnlab ,

Short answer: natively within My Team, there is currently no setting to disable hierarchical inheritance while keeping both tiers active as managers.

Because Docebo builds the My Team tree dynamically from the user-to-manager relationships, as soon as User B has direct reports assigned to them, User A (User B's manager) automatically gets the View team drill-down on User B's card—and more importantly, all of User B's sub-team data automatically rolls up into User A's Courses, Learning Plans, and Reports tabs inside My Team.

In enterprise setups where I've run into this exact requirement, here is the reality of what works and where the roadblocks are:

  • 1. The UI vs. Data Roll-up Trap (Why CSS isn't enough): You can easily hide the View team button on the user cards in the Team Members tab using Custom Styles (CSS). However, that only stops the visual drill-down on that specific tab. As soon as the manager clicks over to the Courses, Learning Plans, or Reports tabs in My Team, Docebo still aggregates the entire downstream hierarchy by default (requiring the manager to manually use the Hierarchy filter to isolate direct reports).

  • 2. The "Manager Types" Limitation: Technically, the View team drill-down is tied to the specific Manager Type tree. While separating management layers into different Manager Types breaks the tree, Docebo caps the platform at 5 Manager Types total, and alternating them creates a messy UX (forcing managers to toggle dropdowns) and complicates notifications and HRIS syncs. It rarely scales past a two-tier edge case.

  • 3. Strict Privacy Requires Moving Outside My Team: If this is driven by strict data privacy or Works Council rules (where upper management legally cannot see skip-level learning data), My Team simply can't enforce that boundary today unless you strip manager permissions from one of the tiers. The only airtight workaround is mapping the org structure to Branches and assigning Power User profiles scoped strictly to their single branch (without descendant branch inheritance)—though you obviously lose the native My Team dashboard UX.

Is this coming up for you as a UI decluttering request (keeping executives from getting overwhelmed by massive sub-trees), or is it a hard data-visibility restriction?

For anyone else following the thread, the hierarchy tree behavior is covered under the Team Members section here:


lrnlab
Hero III
Forum|alt.badge.img+10
  • Author
  • Hero III
  • Nov 10, 2026 9:50 PM UTC

Thx ​@Moshe.Machlav I appreciate the response however the option to make all managers power users and forego the use of the My Team page is not a path we want/can to follow. This is to address a hard view restriction to managers and their direct reports. Even manager types are tough since they limit some options we would like the managers to have. Thanks anyway