Customizable navigation bar with dropdown for external links

yeah there is script option that has been floating around, but indeed, would love non-code option!

Would anyone have an idea where the ‘script option that has been floating around’ may be?  I would like to try and test this out.  We would also like the ability to create more dropdowns using external links and custom page links within the community.

I think ​@olimarrio can hook you up with it?

​@dawn.wayland We made a custom menu as well, and I’d be happy to answer questions and share what I can if it’s helpful.

Hey ​@dawn.wayland & ​@jvdc 👋,

We are implementing this in the coming weeks so you can create custom dropdown with no code, alongside the ability to personalise the menu through our widget visibility functionality depending on what Segment a community member belongs to.

Using custom code is an option but it requires some technical resources depending on the complexity of what you want to build and could require maintenance so I’d recommend waiting for the native functionality. Stay tuned! 

​@olimarrio This is great to hear! We’d love to ditch our custom-coded menu if something native is on the way. 

We currently use custom roles to determine what people have access to. We love the widget visibility functionality, but find that permissioning by segment isn’t as precise as additive permissions by role. Is there any consideration being given to role-based visibility for the menu?

​@olimarrio thank you so much for the update.  Looking forward to seeing it!

I also agree with ​@atwhite on this. 

Nice 🙌 ​@atwhite ​@dawn.wayland - make sure you are signed up for to our Product Updates but you can expect an announcement very soon 👀

​@atwhite Role based permissioning for the mega menu isn’t currently being looked but I’d love to learn more about the limitations you are running into by using Segments for Widget Visibility. Is there a particular use case that it doesn’t solve for? I’m guessing creating Segments that are only filtering on Custom Role doesn’t provide a sufficient workaround for your use case?

​@olimarrio We have four main lines of business, and keep the knowledge bases, forums, etc., for each separate, and we only give access to various areas based on which LOBs a customer uses. Custom Roles work great for this, because we can add as we go. 

With segments, the logic just gets a bit more complex, because we have to account for more variables. For example, sometimes we only care if a person uses one specific line of business; other times, we care if they ONLY have that one line of business.

Additionally, the segment filtering logic doesn’t currently allow us to filter two different ways on one filter. For example, on Custom Roles: we can create a segment for users that definitely have one or more roles, or definitely do not; but we can’t say “has this custom role, but not this custom role.” We can’t create a segment that definitely has both of two given roles. Etc. 

I apologize, I know we’ve run into limitations, but I don't have a specific example directly on hand right now. But I hope this was somewhat helpful!

Thanks for sharing ​@atwhite, it’s definitely helpful - I will feed this back to our Product team so they can take this into account and figure out how we can address this.

In the meantime, I’m pleased to let you all know that we have just released the ability to configure segment visibility and dropdown lists in the mega menu 🙌

You can check out the release notes here.

​@jvdc ​@dawn.wayland ​@atwhite ​@EBrozio 

​@olimarrio amazing, this is great, thank you for the update!

​@olimarrio thank you so much.  Likely user error here but I for the life of me do not see the ‘dropdown’ toggle in Custom pages on my mega menu.  Am I doing something wrong?  Do I need to create a case?

Hi ​@dawn.wayland 👋,

So you can set up these custom dropdown and configure widget visibility for the mega menu across your community rather than particular custom pages.

For example on the Gainsight Community I can add a dropdown menu and then add dropdown menu items by clicking on the ⚙ symbol:

Please let me know if this makes sense or if you have any questions.

​@olimarrio makes total sense, but I am not able to see it and I believe it is because we ‘hid’ the drop down with CSS originally.  Does that make sense?  Assume we need to unhide it if we want to ‘play’ with this.