You actually don’t have to use CSS to achieve this. All you need to do is assign more than one menu to your users. The higher up assigned menu in the hierarchy will control which pages appear in the lefthand menu, while the lower assigned menu in the hierarchy gives the user permission to see the pages assigned to it. 

So I would create a new “Secondary Pages” menu visible to all branches and make it the last menu in your hierarchy. With that, users should no longer see 403 errors on the secondary pages!

I second @nick.tosto on this. I just heard this was possible recently and it’s very helpful. 

@dklinger I attempted to hide menu items via CSS a couple of years ago when we first implemented Docebo. I also took it a step further by indenting menu items to make them appear as ‘subpages’ of parent menu items. It is possible to do via CSS but is ill-advised. If I recall correctly, the biggest issue was the dynamic nature of menus. You’d have to target the specific numbered menu element (e.g., #6). But then that number might change based on the user’s role (e.g., Power User, or a Manager where an additional My Team menu item appears, etc.).

It’s just not worth the hassle IMO. 

Thank you both for the response. @nick.tosto - thank you for the insight. I tried it out and it worked perfectly. I swear I got this wrong actually twice in Docebo University.

As I like to tell people - I am a slower learner - but a learner indeed.

-Dan

I am instituting a best practice to help - dont know if it makes sense - but I figure show it off - so I dont lose the fact that visibility is really being driven by whats up top and the permission to avoid that 403 error is down below.

As I get a little more into it - branch logic - etc - I will be sure to post a better response.

Would OP or any others mind putting together a show-and-tell on how this actually works? Our internal nav is really goofed at the moment. I’ve inherited a system that needs some fixing, but it’s hard to conceptualize while the plane is in flight (if you catch my metaphorical drift).

@willingworth this isn’t a show and tell necessarily, but there are some good step by step instructions on this thread. :-)

Bless you, and those in that thread, @Annarose.Peterson 

We have been using this for our various iterations of our user experience and found it works like a charm. We have 3 multi-domains with multiple experiences in each one.  I love the idea of labeling those that are not visible and will incorporate that ASAP. We had used a pretty vague indicator in the code, but labels would be crystal clear.