Multi-tenancy - resource accesible for all users
Would it be possible for a specific resource open access for all users?
For example, I have a categories resource in which I would like everyone to be able to access all records.
11 Replies
And also that a user, for example the global administrator, without belonging to any of the Teams can have access to everything?
I can assign access to all the Teams and will be able to see everything, but user have to select one by one and I would like you to see everything without having to go one by one.
At the moment what I did is create a new panel with the same resources and pages and in one of them remove the tenant()
Would it be possible to hide a resource in a specific panel?
You should be able to do this with policies
@toeknee Well not in the tenant panel... But yeah, you could do this with separate panels. The tenant id is scoped to everything registered in a panel with tenancy.
like creating "global" panel and permit everyone to access?
Yeah you would have to create a separate panel that doesn't have tenancy
What about creating a specific directory of global resources then set each panel to discover the resource in that directory?
Yeah I think better to create some "global panel" for easier command, and prevent that panel to be registered in service provider while other panel discovers its resources
Yeah I'm not really sure what you mean or if that would work, but probably not...
Im just talking about creating a separate panel without tenancy
separate panel has its own resources and path, so we still need to manually register the navmenu right?
I dont think so, depends on what you are talking about... Can you be more specific?
I think we're still talking about the thread
Let's say we create panel named "global" without tenancy, make CategoryResource there, then the other panels i.e. Tenant and Admin panels, they both discover the CategoryResource, and don't forget to maintain the policy
Then to make sure the Global panel itself is not accessible (we only need the shared resources, and the advantage of artisan commands), we don't register it to the app...
Umm yeah I guess...