Update doc for project permissions and groups

doc/project-permissions.markdown

@@ -1,49 +1,23 @@
-Project permissions
+Project Permissions
 ===================
 
-A project can have two kinds of people: **project managers** and **project members**.
+Each project is isolated and compartmented from each other.
+The project access must be allowed by the project owner.
 
-- Project managers can manage the configuration of the project and access to the reports.
-- Project members can only do basic operations (create or move tasks).
+Each user and each group can have a different role assigned.
+There are 3 types of [roles for projects](roles.markdown):
 
-When you create a new project, you are automatically assigned as a project manager.
+- Project Manager
+- Project Member
+- Project Viewer
 
-Kanboard administrators can access to everything but they are not necessary project members or managers. **Those permissions are defined at the project level**.
+Only administrators have access to everything.
 
-Permissions for each role
--------------------------
+Roles assignation is available from **Project Settings > Permissions**:
 
-### Project members
+![Project Permissions](screenshots/project-permissions.png)
 
-- Use the board (create, move and edit tasks)
-- Remove only tasks created by themselves
+If you choose to allow everybody, all Kanboard users will be considered Project Member.
+That also means there is no role management anymore. Permissions per user or per group cannot be applied.
 
-### Project managers
-
-- Use the board
-- Configure the project
-	- Share, rename, duplicate and disable the project
-	- Manage swimlanes, categories, columns and users
-	- Edit automatic actions
-- CSV Exports
-- Remove tasks of any project members
-- Access to the analytics section
-
-They **cannot remove the project**.
-
-Manage users and permissions
-----------------------------
-
-To define project roles, go to the **project configuration page** then click on **User management**.
-
-### User management
-
-![Project permissions](http://kanboard.net/screenshots/documentation/project-permissions.png)
-
-From there, you can choose to add new members, change the role or revoke user access.
-
-### Allow everybody
-
-If you choose to allow everybody (all Kanboard users), the project is considered public.
-
-That means there is no role management anymore. Permissions per user cannot be applied.
+Private projects cannot define permissions.