Not sure how to use gates/policies with permissions

[AidasK]

Not sure when I should define a gate and when a permission. It looks like that everything can be handled via permissions, but it would be great to have some guidance how to organise all of this. As it looks like I could just drop gates and policies, though it feels wrong.

My current requirements:

• each route should be controlled
• each resource(model) should be controlled as it's done in Policies
• some inner blade widgets should not be seen by other roles

My approach was to handle each named route with separate Gate. New route, new gate. So gates file is the same size as routes.
Manage resources via Policy
Manage custom view widgets via Policies or gates (depends if it requires a resource)

Each gate and policy just does a proxy to hasAccess: " Gate::define('handle-paypal', fn (User $user) => $user->hasAccess('handle-paypal'));".

My approach feels a bit wrong. It's questionable why orchid hasn't endorsed Policy/Gate way to do it, but instead introduced new "permissions" concept. It does not look any different from gate.

Can you share your way how you manage this? Would be great to have cons/pros list of it.

[AidasK]

Still interested how gates/policies plays along with permissions in practice.