If there's an official document for this, I can't find it. That would be helpful.

Based on my experience so far, this is fairly straightforward, that is, if you've worked with file permissions in the past. Each permissions either enables or disables your ability to perform the function associated with it. For these items, this seems self-explanatory:

• Browse Node
• Edit in Canvas
• Create
• Delete
• Move
• Copy
• Sort (To answer your question, this enables your ability to change the sort order of nodes in the content or media tree. This order tends to ripple out depending on how you've structured your rendering of node items in list views)
• Permissions
• Rollback
• Update

For these however, I'm not clear:
(Publish I get, but "send to publish?" Is this a "lying-in-wait" widget for a workflow?)
• Publish
• Send To Publish
(Similar question for these two, I'm guessing you have to enable translation processes)
• Send To Translation
• Translate
(I suppose this enables the capture of who edited which node -- though where you find that information, I don't know)
• Audit Trail
(I'm unclear on the "hostnames" or "public access" concepts in umbraco but I imagine if I understood it, this permission is straightforward)
• Manage hostnames
• Public access

Manage hostnames can be used to host multiple domains (or sub domains) on the same umbraco installation. You use manage hostnames at the home folders of your sites and put in the domain names. 

Public access is used to password protect pages (either simple, with a single username/password or advanced, using the members area)

Send to publish is used for workflow which alread exists. the user type 'editor' (IIRC), doesn't have publish permissions, only send to publish permissions. I think you need to use an ActionHandler to implement your own workflow (i.e. to email a publisher, etc....)

Similar to the 'editor', there is a translator user type. When a translator logs in, they get the translate application which allows them to update all of the dictionary items that are missing. I'm not sure if you need to implement your own ActionHandler to get this workflow going as well.

All permission items are based on an interface called IAction. You can actually create your own permission item and as long as your return true for the IsPermissionAssignable (i think) property, it will show up in your permissions list. This way could create custom permission items which you could use in a custom tree, dialog, or whatever. It's also a way that allows you to create your own workflow structure since you can use ActionHandlers to listen to any permission/IAction.

I'm looking to implement a rename permission for v4.1 so we can remove a users rights to rename as this will generally change the URL for that node and in some cases, people have coded their application to be dependant on a name. This also means that i'll be able to implement inline renaming of nodes with the new tree framework so you don't have to go edit the page to change the name.

is working on a reply...