summaryrefslogtreecommitdiff
path: root/doc/project-permissions.markdown
diff options
context:
space:
mode:
Diffstat (limited to 'doc/project-permissions.markdown')
-rw-r--r--doc/project-permissions.markdown12
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/project-permissions.markdown b/doc/project-permissions.markdown
index 16586bc6..99e4caa2 100644
--- a/doc/project-permissions.markdown
+++ b/doc/project-permissions.markdown
@@ -1,8 +1,8 @@
Project Permissions
===================
-Each project is isolated and compartmented from each other.
-The project access must be allowed by the project owner.
+Each project is isolated from other projects.
+Project access must be allowed by the project owner.
Each user and each group can have a different role assigned.
There are 3 types of [roles for projects](roles.markdown):
@@ -13,11 +13,11 @@ There are 3 types of [roles for projects](roles.markdown):
Only administrators have access to everything.
-Roles assignation is available from **Project Settings > Permissions**:
+Role assignments are visible in **Project Settings > Permissions**:
![Project Permissions](screenshots/project-permissions.png)
-If you choose to allow everybody, all Kanboard users will be considered Project Member.
-That also means there is no role management anymore. Permission per user or per group cannot be applied.
+If you choose to allow everybody, all Kanboard users will be considered 'Project Member'.
+With this setting, role management will have no effect. Permission per user or per group cannot be applied.
-Private projects cannot define permission.
+Private projects cannot define permissions.