A team leader cannot see a page, group or command
Review page permissions, action permissions and live resource visibility as three distinct checks.
Recognize the symptom
One account can open a page but has fewer commands or resources than another. Alternatively, the entire page is absent from navigation. Note exactly what is missing and whether the account uses the normal or dedicated Display session profile.
Possible causes
A reusable profile or custom permission set may exclude the page or action. Live resource scopes can exclude queue groups or extensions. Shared hidden resources and personal preferences can further reduce what appears. Display sessions deliberately restrict access to their supported read-only use.
Check before changing anything
In Users, inspect the account’s role, permission mode, assigned profile and session profile. Then inspect queue scope for Dashboard, Wallboard and Videowall, and the separate Monitor and Status scopes. Finally review shared Operational views and that account’s personal visibility choices.
Take a targeted action
Grant only the intended page, action or live resources and save at the correct level. Editing a shared profile can affect several users, while a personal preference cannot grant new permissions. Do not use administrator role simply to bypass an unexplained visibility problem.
Verify the result
Test a fresh session using the affected account and confirm both allowed and excluded items. Live resource scopes currently do not filter historical reports, exports or recordings by queue. Check their page and action permissions separately rather than assuming the live scope protects every dataset.