bump version to 4.3-5

[pve-docs.git] / pveum.adoc

diff --git a/pveum.adoc b/pveum.adoc
index 9addcb7bc8827abfa77b81c0138e6ea24b52078c..cca1ece134424c00f1da067c743acc29f1db8e13 100644 (file)
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -9,7 +9,7 @@ NAME
 pveum - Proxmox VE User Manager
 
 
-SYNOPSYS
+SYNOPSIS
 --------
 
 include::pveum.1-synopsis.adoc[]
@@ -309,20 +309,6 @@ Some examples are:
 * `/access/realms/{realmid}`: Administrative access to realms
 
 
-Permissions
-~~~~~~~~~~~
-
-Permissions are the way we control access to objects. In technical
-terms they are simply a triple containing `<path,user,role>`. This
-concept is also known as access control lists. Each permission
-specifies a subject (user or group) and a role (set of privileges) on
-a specific path.
-
-When a subject requests an action on an object, the framework looks up
-the roles assigned to that subject (using the object path). The set of
-roles defines the granted privileges.
-
-
 Inheritance
 ^^^^^^^^^^^