Thread automatically created by sillygirrrl in #740893011994738751

Hello @freezing-cricket-25904 yes, that's the correct way

besides that the button still appears: #part of the code in the resource: tabs do field pets, as: :has_many, show_on: :edit end #part in the model: has_many :pets, inverse_of: , dependent: :nullify #part in the policies def attach_pets? false end

Do you possess a pro license?

mmh i don't think so

Authorization is a pro feature

ohh... okay i get it

Mmh Despite that, would this be the correct way? I don't know if the project I work on is pro, but I see that it has policy implementations by a 'role.'

Yes, is the correct way, the policy implementation can be unrelated to avo, if you acquire the pro license you can add the

def attach_pets?

to that policy implementations and it should work

Thank you

You're welcome! Let us know if still not working with a pro license