* added permission concept to README_FOR_APP

1 files changed, 23 insertions, 4 deletions

diff --git a/doc/README_FOR_APP b/doc/README_FOR_APP
index b0178eb..1266d7c 100644
--- a/doc/README_FOR_APP
+++ b/doc/README_FOR_APP
@@ -87,13 +87,13 @@ that draft or the lock on it, enabling other users to edit that page again.
 
 ===Tags
 
-Pages of course come with meta data attatched to them. Tags are one kind of
+Pages of course come with meta data attached to them. Tags are one kind of
 meta data. They can be understood and used as keywords, categories, tags or any 
 similar concept.
 
 ===Templates
 
-Althought there is only one, simple and unified, template for editing pages, it 
+Although there is only one, simple and unified, template for editing pages, it 
 is possible to select from different templates for public display. This 
 selection of templates allows slight alterations of the layout. For example one
 template would display every attribute of a page (like date, author, abstract)
@@ -102,7 +102,7 @@ of a page, another wouldn't.
 
 ===Aggregation
 
-Keywords and other meta data can be used to aggregate any ammount of pages
+Keywords and other meta data can be used to aggregate any amount of pages
 into the body of another page. 
 
 <aggregate 
@@ -110,4 +110,23 @@ into the body of another page.
   limit="20"
   order_by="published_at"
   order_direction="DESC"
-/>
\ No newline at end of file
+/>
+
+===Permissions
+
+The permission system is geared towards our use-case which means you won't find
+the standard create/update/destroy derived permissions.
+Every user without having any permissions is allowed to perform non-destructive
+tasks that won't affect the frontend (published pages). What am I talking about?
+
+Bob has no permissions whatsoever still he is allowed to edit a #Page anywhere, because this action will only create a new revision of the #Page which is not immediately published. He won't be able to manipulate a #Node in any way (unique_name, slug, ordering, structure) because this would affect the frontend
+without further notice.
+
+Having a #Permission on a #Node makes Bob an admin for this #Node and all it's
+children. Now Bob can do pretty much anything on these nodes including such fun
+things as:
+        - Create/Update/Delete a #Node
+        - Reorder children of the #Node
+        - Rejecting a draft and telling the author to get his/her spelling right.
+        - Clear a stale lock on a #Node
+        
\ No newline at end of file