X-Git-Url: https://git.proxmox.com/?a=blobdiff_plain;ds=sidebyside;f=pveum.adoc;h=95406c9874282224acd33e3583501b69a1df71e7;hb=0d02df33f12a84b417a6806e0d3faa51d1ad7b53;hp=9350be9c95900c7f1982f5ce6513ce8b60948a8f;hpb=404a158e1b79f205df7f5cf1827dde32ef9a8ea2;p=pve-docs.git

diff --git a/pveum.adoc b/pveum.adoc
index 9350be9..95406c9 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -1,6 +1,7 @@
+[[chapter_user_management]]
 ifdef::manvolnum[]
-PVE(1)
-======
+pveum(1)
+========
 include::attributes.txt[]
 :pve-toplevel:
 
@@ -19,16 +20,12 @@ include::pveum.1-synopsis.adoc[]
 DESCRIPTION
 -----------
 endif::manvolnum[]
-
 ifndef::manvolnum[]
 User Management
 ===============
 include::attributes.txt[]
-endif::manvolnum[]
-
-ifdef::wiki[]
 :pve-toplevel:
-endif::wiki[]
+endif::manvolnum[]
 
 // Copied from pve wiki: Revision as of 16:10, 27 October 2015
 
@@ -40,12 +37,13 @@ By using the role based user- and permission management for all
 objects (VMs, storages, nodes, etc.) granular access can be defined.
 
 
+[[pveum_users]]
 Users
 -----
 
 {pve} stores user attributes in `/etc/pve/user.cfg`.
 Passwords are not stored here, users are instead associated with
-<<authentication-realms,authentication realms>> described below.
+<<pveum_authentication_realms,authentication realms>> described below.
 Therefore a user is internally often identified by its name and
 realm in the form `<userid>@<realm>`.
 
@@ -70,6 +68,7 @@ still be changed and system mails will be sent to the email address
 assigned to this user.
 
 
+[[pveum_groups]]
 Groups
 ~~~~~~
 
@@ -79,7 +78,7 @@ to groups instead of using individual users. That way you will get a
 much shorter access control list which is easier to handle.
 
 
-[[authentication-realms]]
+[[pveum_authentication_realms]]
 Authentication Realms
 ---------------------
 
@@ -188,6 +187,7 @@ https://developers.yubico.com/Software_Projects/YubiKey_OTP/YubiCloud_Validation
 host your own verification server].
 
 
+[[pveum_permission_management]]
 Permission Management
 ---------------------
 
@@ -203,6 +203,7 @@ role)', with the role containing a set of allowed actions, and the path
 representing the target of these actions.
 
 
+[[pveum_roles]]
 Roles
 ~~~~~
 
@@ -326,6 +327,7 @@ by default). We use the following inheritance rules:
 * Permissions replace the ones inherited from an upper level.
 
 
+[[pveum_pools]]
 Pools
 ~~~~~