How do you model creation permissions? If there is no resource on which to relate a subject how can we define that an

admin

can for example create any resource of type

B

in our architecture?

You can create a singleton "root" or "platform" object definition where resources hang from and put the definition there

Ok, that's also where me and team where heading towards, thanks for confirming.

Anytime!

@Lurian the other part of it is that you put the create permission on the parent object - so if it's a file the creation permission goes on the project or folder, if it's a repo the creation permission goes on the organization, etc