Let's say I create a Z Class "Document" and define some new permission types. Then for some objects in my Z Class I create permission mappings, such as "Add Documents, Images, and Files" and "Delete objects" mapping to my permission type "Manage documents". Then I create some instances of the Z Class in the folder "Documents". I define a new global role "DocumentAdmin". I want this role to manage documents in the "Documents" folder and all subfolders. But there's the rub. I'd like to use acquisition to enable these security settings for all documents in this hierarchy. Zope only allows giving this permission to this role for each and every specific Z Class instance, because my custom permissions, such as "Manage documents", are not available on the folder level -- they're only available on instances. Is this a bug? Isn't the permission list supposed to be a superset of all available permission types defined in the database? Am I missing something? Because of this design, I guess I have to create a dummy Z Class called "DocumentFolder" which defines my custom permissions, then let the root folder be an instance of this class. Which is fine, but I didn't expect having to do this. If this is by design, I'd like to know the rationale behind it. Oh, and this is Zope 1.11.0pr1. -- Alexander Staubo http://www.mop.no/~alex/ "`Ford, you're turning into a penguin. Stop it.'" --Douglas Adams, _The Hitchhiker's Guide to the Galaxy_