Automic Workload Automation

I am new to Automic but have been asked to design some authorization schemes for developers and users but have many questions.  I have read the documentation on planning an authorization system, authorizations and permissions.  

What I am looking for is a best practices guide for setting up authorizations and permissions to answer some of the questions below and others I haven't found yet.  Does such a document exist?

Authorizations seem to be very specific.  i.e., no inherited rights to child folder so you have to identify every folder you want authorized. Can it be dynamic?  If I add a sub folder, can the user inherit the rights of the parent folder?  Then it talks about authorization groups 1 to 9.  If I use 1 all works fine, if I add a 2, then 1 no longer works.  I understand the logical OR but not sure how "Access rights defined for an authorization group thus sum up" if group 2 overrides group 1.  Then if you create a user group, which takes priority, user or group?  The documentation wasn't clear to me.  Would it be better to create a user group with extensive authorizations but limit user authorizations? or vice versa?

For permissions, it seems more of check this and it does that but not which permissions should be minimum.  What authorizations/permissions should a developer have versus a user? 

Any direction would be greatly appreciated.

You can start with a naming concept - see document mentioned here:
https://community.automic.com/discussion/9498/object-naming-standards-question

Basically every right for an object has to be assigned via its name.

Yes, there ist no heritage for any object or folder :-)

You can either use positive logic (grant special right to users) or - if the structure in your company is not that complex - negative logic by explicitly denying access to objects for users.

If the structure of your authorization system and the amount of different users or user groups is big at all I would suggest purchasing a consultant from automic for a day or two - because planning and setting up an authorization system is not that easy cheesy task within Automic...

Thanks Wolfgang.  I will look at the document.