Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Navigation - Disabled vs Hide vs Empty state #3922

Open
mmenestr opened this issue Mar 18, 2024 · 1 comment
Open

Navigation - Disabled vs Hide vs Empty state #3922

mmenestr opened this issue Mar 18, 2024 · 1 comment

Comments

@mmenestr
Copy link
Collaborator

Would like to add more guidance around navigation, and what to do when someone shouldn't have access to it.
Describe that we do not recommend disabling the nav item - and we do not offer that option in PF, but we instead recommend either hiding it, or having an empty state once the user lands on the page, informing them why they can't access it.

@mmenestr
Copy link
Collaborator Author

mmenestr commented May 6, 2024

@edonehoo we can work on this one together if you want since this is very product specific / I can write up a draft and we can go from there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Not started
Development

No branches or pull requests

2 participants