scan-adoc-refs: improve title parser, store doctype

[pve-docs.git] / pveum.adoc

diff --git a/pveum.adoc b/pveum.adoc
index 9addcb7bc8827abfa77b81c0138e6ea24b52078c..c83945e2cd1e6bc20a4db14fcf8ec80e208a9c8a 100644 (file)
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -3,13 +3,15 @@ PVE({manvolnum})
 ================
 include::attributes.txt[]
 
+:pve-toplevel:
+
 NAME
 ----
 
 pveum - Proxmox VE User Manager
 
 
-SYNOPSYS
+SYNOPSIS
 --------
 
 include::pveum.1-synopsis.adoc[]
@@ -25,6 +27,10 @@ User Management
 include::attributes.txt[]
 endif::manvolnum[]
 
+ifdef::wiki[]
+:pve-toplevel:
+endif::wiki[]
+
 // Copied from pve wiki: Revision as of 16:10, 27 October 2015
 
 Proxmox VE supports multiple authentication sources, e.g. Linux PAM,
@@ -309,20 +315,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
 ^^^^^^^^^^^