Access Policies and Access Manager

Really impressed with the flexability of Revolution.

I’m on beta 5 - and had a question: When an access policy prohibits a certain action - is there any way of hiding a corresponding action menu item?

Alternatively - is there away to access said functions if they’re not in the ’actions’ menu somewhere?

Thanks!!

I would imagine that hiding things on menus is done using form customization. I haven’t figured out exactly how FC works, mainly struggling with what fields and containing panels to use for hiding menu items. but my understanding is that it should be possible.

Having these permissions in a policy allows the following:

Resource Tree

• edit_context - "Update Context"
• new_document - Any of the Create and Quick Create Resource items, and Duplicate option
• view_document - "View Resource"
• edit_document - "Edit Resource" and "Quick Update Resource"
• save_document - Unpublish/Publish and Delete/Undelete

Element Tree
Basically, the same idea as the Resource tree; just substitute "document" with the Element type (chunk, tv, template, etc).

The context menu stuff will probably be fine-tuned in pre-RC1 commits.

What about "load" ?

Quote from: BobRay at Dec 15, 2009, 05:00 PM

What about "load" ?

"Load" loads an object, and is object-driven, not action-driven, so...removing load will prevent any Resources from showing.

Can load be tied to a resource group, or is it all or nothing?

Quote from: BobRay at Dec 15, 2009, 07:19 PM

Can load be tied to a resource group, or is it all or nothing?

The basic permissions like "load", "save", "remove" apply to Resources or Contexts (and in the future any other class that is a derivative of modAccessibleObject). So yes, "load" is required to even be able to get a Resource in a Resource Group from the database, just like "save" controls the ability to save changes to that object to the database, and "remove" controls the ability to delete the row from the database. For clarification, "delete" is reserved for marking an object for deletion in the database vs. actually removing the row from the database entirely, i.e. "delete" = move to trash.