© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
FilamentF
Filament•16mo ago•
1 reply
Bruno Pereira

Bug? regarding clusters navigation

So I have some clusters assigned to some resources and when I override the canAccess and shouldRegisterNAvigation function in the cluster class. It disables the main cluster route but not the resources ones. The user can manually type the url and access it.

Example:

Cluster = Settings::class (url = /settings),

User Resource uses Settings cluster (url = /settings/users).

return false on both functions the result is

/settings gives 403 but /settings/users gives 200 and can access everything related to the resource.

Is it intended and I should fiddle with the canAccess of the resource or a bug?

Thanks
Filament banner
FilamentJoin
A powerful open source UI framework for Laravel • Build and ship admin panels & apps fast with Livewire
20,307Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

Order of Clusters in Navigation
FilamentFFilament / ❓┊help
15mo ago
Navigation Parent Items in Clusters
FilamentFFilament / ❓┊help
2y ago
Question regarding navigation groups
FilamentFFilament / ❓┊help
2y ago
Clusters: Account Settings with Sub-Navigation has changed?
FilamentFFilament / ❓┊help
2y ago