]>
Commit | Line | Data |
---|---|---|
80c0adcb | 1 | [[chapter_user_management]] |
3c8533f2 | 2 | ifdef::manvolnum[] |
b2f242ab DM |
3 | pveum(1) |
4 | ======== | |
38fd0958 | 5 | include::attributes.txt[] |
5f09af76 DM |
6 | :pve-toplevel: |
7 | ||
3c8533f2 DM |
8 | NAME |
9 | ---- | |
10 | ||
11 | pveum - Proxmox VE User Manager | |
12 | ||
13 | ||
49a5e11c | 14 | SYNOPSIS |
3c8533f2 DM |
15 | -------- |
16 | ||
17 | include::pveum.1-synopsis.adoc[] | |
18 | ||
19 | ||
20 | DESCRIPTION | |
21 | ----------- | |
22 | endif::manvolnum[] | |
3c8533f2 DM |
23 | ifndef::manvolnum[] |
24 | User Management | |
25 | =============== | |
38fd0958 | 26 | include::attributes.txt[] |
5f09af76 | 27 | :pve-toplevel: |
194d2f29 | 28 | endif::manvolnum[] |
5f09af76 | 29 | |
3c8533f2 DM |
30 | // Copied from pve wiki: Revision as of 16:10, 27 October 2015 |
31 | ||
5462c161 WB |
32 | Proxmox VE supports multiple authentication sources, e.g. Linux PAM, |
33 | an integrated Proxmox VE authentication server, LDAP, Microsoft Active | |
34 | Directory. | |
3c8533f2 DM |
35 | |
36 | By using the role based user- and permission management for all | |
5eba0743 FG |
37 | objects (VMs, storages, nodes, etc.) granular access can be defined. |
38 | ||
3c8533f2 | 39 | |
80c0adcb | 40 | [[pveum_users]] |
c80b9ee6 WB |
41 | Users |
42 | ----- | |
43 | ||
44 | {pve} stores user attributes in `/etc/pve/user.cfg`. | |
45 | Passwords are not stored here, users are instead associated with | |
80c0adcb | 46 | <<pveum_authentication_realms,authentication realms>> described below. |
c80b9ee6 WB |
47 | Therefore a user is internally often identified by its name and |
48 | realm in the form `<userid>@<realm>`. | |
49 | ||
50 | Each user entry in this file contains the following information: | |
51 | ||
52 | * First name | |
53 | * Last name | |
54 | * E-mail address | |
55 | * Group memberships | |
56 | * An optional Expiration date | |
57 | * A comment or note about this user | |
58 | * Whether this user is enabled or disabled | |
59 | * Optional two factor authentication keys | |
60 | ||
61 | ||
62 | System administrator | |
63 | ~~~~~~~~~~~~~~~~~~~~ | |
64 | ||
65 | The system's root user can always log in via the Linux PAM realm and is an | |
66 | unconfined administrator. This user cannot be deleted, but attributes can | |
67 | still be changed and system mails will be sent to the email address | |
68 | assigned to this user. | |
69 | ||
70 | ||
80c0adcb | 71 | [[pveum_groups]] |
c80b9ee6 WB |
72 | Groups |
73 | ~~~~~~ | |
74 | ||
75 | Each user can be member of several groups. Groups are the preferred | |
76 | way to organize access permissions. You should always grant permission | |
77 | to groups instead of using individual users. That way you will get a | |
78 | much shorter access control list which is easier to handle. | |
79 | ||
80 | ||
80c0adcb | 81 | [[pveum_authentication_realms]] |
3c8533f2 DM |
82 | Authentication Realms |
83 | --------------------- | |
84 | ||
d6614202 WB |
85 | As {pve} users are just counterparts for users existing on some external |
86 | realm, the realms have to be configured in `/etc/pve/domains.cfg`. | |
87 | The following realms (authentication methods) are available: | |
3c8533f2 DM |
88 | |
89 | Linux PAM standard authentication:: | |
d6614202 WB |
90 | In this case a system user has to exist (eg. created via the `adduser` |
91 | command) on all nodes the user is allowed to login, and the user | |
92 | authenticates with their usual system password. | |
93 | + | |
3c8533f2 DM |
94 | [source,bash] |
95 | ---- | |
96 | useradd heinz | |
97 | passwd heinz | |
98 | groupadd watchman | |
99 | usermod -a -G watchman heinz | |
100 | ---- | |
101 | ||
102 | Proxmox VE authentication server:: | |
d6614202 WB |
103 | This is a unix like password store (`/etc/pve/priv/shadow.cfg`). |
104 | Password are encrypted using the SHA-256 hash method. | |
105 | This is the most convenient method for for small (or even medium) | |
106 | installations where users do not need access to anything outside of | |
107 | {pve}. In this case users are fully managed by {pve} and are able to | |
108 | change their own passwords via the GUI. | |
109 | ||
110 | LDAP:: | |
111 | It is possible to authenticate users via an LDAP server (eq. | |
112 | openldap). The server and an optional fallback server can be | |
113 | configured and the connection can be encrypted via SSL. | |
114 | + | |
115 | Users are searched under a 'Base Domain Name' (`base_dn`), with the | |
116 | user name found in the attribute specified in the 'User Attribute Name' | |
117 | (`user_attr`) field. | |
118 | + | |
119 | For instance, if a user is represented via the | |
120 | following ldif dataset: | |
121 | + | |
122 | ---- | |
123 | # user1 of People at ldap-test.com | |
124 | dn: uid=user1,ou=People,dc=ldap-test,dc=com | |
125 | objectClass: top | |
126 | objectClass: person | |
127 | objectClass: organizationalPerson | |
128 | objectClass: inetOrgPerson | |
129 | uid: user1 | |
130 | cn: Test User 1 | |
131 | sn: Testers | |
132 | description: This is the first test user. | |
133 | ---- | |
134 | + | |
135 | The 'Base Domain Name' would be `ou=People,dc=ldap-test,dc=com` and the user | |
136 | attribute would be `uid`. | |
137 | + | |
138 | If {pve} needs to authenticate (bind) to the ldap server before being | |
139 | able to query and authenticate users, a bind domain name can be | |
140 | configured via the `bind_dn` property in `/etc/pve/domains.cfg`. Its | |
141 | password then has to be stored in `/etc/pve/priv/ldap/<realmname>.pw` | |
142 | (eg. `/etc/pve/priv/ldap/my-ldap.pw`). This file should contain a | |
143 | single line containing the raw password. | |
144 | ||
145 | Microsoft Active Directory:: | |
3c8533f2 | 146 | |
d6614202 WB |
147 | A server and authentication domain need to be specified. Like with |
148 | ldap an optional fallback server, optional port, and SSL | |
149 | encryption can be configured. | |
3c8533f2 | 150 | |
5eba0743 | 151 | |
9e8f2770 WB |
152 | Two factor authentication |
153 | ------------------------- | |
154 | ||
155 | Each realm can optionally be secured additionally by two factor | |
156 | authentication. This can be done by selecting one of the available methods | |
157 | via the 'TFA' dropdown box when adding or editing an Authentication Realm. | |
158 | When a realm has TFA enabled it becomes a requirement and only users with | |
159 | configured TFA will be able to login. | |
160 | ||
161 | Currently there are two methods available: | |
162 | ||
163 | Time based OATH (TOTP):: | |
164 | This uses the standard HMAC-SHA1 algorithm where the current time is hashed | |
165 | with the user's configured key. The time step and password length | |
166 | parameters are configured. | |
167 | + | |
168 | A user can have multiple keys configured (separated by spaces), and the | |
169 | keys can be specified in Base32 (RFC3548) or hexadecimal notation. | |
170 | + | |
171 | {pve} provides a key generation tool (`oathkeygen`) which prints out a | |
172 | random key in Base32 notation which can be used directly with various OTP | |
173 | tools, such as the `oathtool` command line tool, the Google authenticator | |
174 | or FreeOTP Android apps. | |
175 | ||
176 | YubiKey OTP:: | |
177 | For authenticating via a YubiKey a Yubico API ID, API KEY and validation | |
178 | server URL must be configured, and users must have a YubiKey available. In | |
179 | order to get the key ID from a YubiKey, you can trigger the YubiKey once | |
180 | after connecting it to USB and copy the first 12 characters of the typed | |
181 | password into the user's 'Key IDs' field. | |
182 | + | |
183 | Please refer to the | |
184 | https://developers.yubico.com/OTP/[YubiKey OTP] documentation for how to use the | |
185 | https://www.yubico.com/products/services-software/yubicloud/[YubiCloud] or | |
186 | https://developers.yubico.com/Software_Projects/YubiKey_OTP/YubiCloud_Validation_Servers/[ | |
187 | host your own verification server]. | |
188 | ||
189 | ||
80c0adcb | 190 | [[pveum_permission_management]] |
04f44730 | 191 | Permission Management |
3c8533f2 DM |
192 | --------------------- |
193 | ||
04f44730 WB |
194 | In order for a user to perform an action (such as listing, modifying or |
195 | deleting a parts of a VM configuration), the user needs to have the | |
196 | appropriate permissions. | |
197 | ||
198 | {pve} uses a role and path based permission management system. An entry in | |
199 | the permissions table allows a user or group to take on a specific role | |
200 | when accessing an 'object' or 'path'. This means an such an access rule can | |
201 | be represented as a triple of '(path, user, role)' or '(path, group, | |
202 | role)', with the role containing a set of allowed actions, and the path | |
203 | representing the target of these actions. | |
204 | ||
5eba0743 | 205 | |
80c0adcb | 206 | [[pveum_roles]] |
853d288b WB |
207 | Roles |
208 | ~~~~~ | |
209 | ||
210 | A role is simply a list of privileges. Proxmox VE comes with a number | |
211 | of predefined roles which satisfies most needs. | |
212 | ||
213 | * `Administrator`: has all privileges | |
214 | * `NoAccess`: has no privileges (used to forbid access) | |
215 | * `PVEAdmin`: can do most things, but miss rights to modify system settings (`Sys.PowerMgmt`, `Sys.Modify`, `Realm.Allocate`). | |
216 | * `PVEAuditor`: read only access | |
217 | * `PVEDatastoreAdmin`: create and allocate backup space and templates | |
218 | * `PVEDatastoreUser`: allocate backup space and view storage | |
219 | * `PVEPoolAdmin`: allocate pools | |
220 | * `PVESysAdmin`: User ACLs, audit, system console and system logs | |
221 | * `PVETemplateUser`: view and clone templates | |
222 | * `PVEUserAdmin`: user administration | |
223 | * `PVEVMAdmin`: fully administer VMs | |
224 | * `PVEVMUser`: view, backup, config CDROM, VM console, VM power management | |
225 | ||
226 | You can see the whole set of predefined roles on the GUI. | |
227 | ||
228 | Adding new roles can currently only be done from the command line, like | |
229 | this: | |
230 | ||
231 | [source,bash] | |
232 | ---- | |
233 | pveum roleadd PVE_Power-only -privs "VM.PowerMgmt VM.Console" | |
234 | pveum roleadd Sys_Power-only -privs "Sys.PowerMgmt Sys.Console" | |
235 | ---- | |
236 | ||
237 | ||
3c8533f2 DM |
238 | Privileges |
239 | ~~~~~~~~~~ | |
240 | ||
241 | A privilege is the right to perform a specific action. To simplify | |
242 | management, lists of privileges are grouped into roles, which can then | |
0e1fda70 WB |
243 | be used in the permission table. Note that privileges cannot directly be |
244 | assigned to users and paths without being part of a role. | |
3c8533f2 DM |
245 | |
246 | We currently use the following privileges: | |
247 | ||
248 | Node / System related privileges:: | |
249 | ||
250 | * `Permissions.Modify`: modify access permissions | |
251 | * `Sys.PowerMgmt`: Node power management (start, stop, reset, shutdown, ...) | |
252 | * `Sys.Console`: console access to Node | |
253 | * `Sys.Syslog`: view Syslog | |
254 | * `Sys.Audit`: view node status/config | |
255 | * `Sys.Modify`: create/remove/modify node network parameters | |
256 | * `Group.Allocate`: create/remove/modify groups | |
257 | * `Pool.Allocate`: create/remove/modify a pool | |
258 | * `Realm.Allocate`: create/remove/modify authentication realms | |
259 | * `Realm.AllocateUser`: assign user to a realm | |
260 | * `User.Modify`: create/remove/modify user access and details. | |
261 | ||
262 | Virtual machine related privileges:: | |
263 | ||
264 | * `VM.Allocate`: create/remove new VM to server inventory | |
265 | * `VM.Migrate`: migrate VM to alternate server on cluster | |
266 | * `VM.PowerMgmt`: power management (start, stop, reset, shutdown, ...) | |
267 | * `VM.Console`: console access to VM | |
268 | * `VM.Monitor`: access to VM monitor (kvm) | |
269 | * `VM.Backup`: backup/restore VMs | |
270 | * `VM.Audit`: view VM config | |
271 | * `VM.Clone`: clone/copy a VM | |
272 | * `VM.Config.Disk`: add/modify/delete Disks | |
273 | * `VM.Config.CDROM`: eject/change CDROM | |
274 | * `VM.Config.CPU`: modify CPU settings | |
275 | * `VM.Config.Memory`: modify Memory settings | |
276 | * `VM.Config.Network`: add/modify/delete Network devices | |
277 | * `VM.Config.HWType`: modify emulated HW type | |
278 | * `VM.Config.Options`: modify any other VM configuration | |
279 | * `VM.Snapshot`: create/remove VM snapshots | |
280 | ||
281 | Storage related privileges:: | |
282 | ||
283 | * `Datastore.Allocate`: create/remove/modify a data store, delete volumes | |
284 | * `Datastore.AllocateSpace`: allocate space on a datastore | |
285 | * `Datastore.AllocateTemplate`: allocate/upload templates and iso images | |
286 | * `Datastore.Audit`: view/browse a datastore | |
287 | ||
5eba0743 | 288 | |
b8eeec52 WB |
289 | Objects and Paths |
290 | ~~~~~~~~~~~~~~~~~ | |
291 | ||
292 | Access permissions are assigned to objects, such as a virtual machines, | |
293 | storages or pools of resources. | |
294 | We use file system like paths to address these objects. These paths form a | |
295 | natural tree, and permissions of higher levels (shorter path) can | |
296 | optionally be propagated down within this hierarchy. | |
297 | ||
7d48940b | 298 | [[pveum_templated_paths]] |
b8eeec52 WB |
299 | Paths can be templated. When an API call requires permissions on a |
300 | templated path, the path may contain references to parameters of the API | |
301 | call. These references are specified in curly braces. Some parameters are | |
302 | implicitly taken from the API call's URI. For instance the permission path | |
303 | `/nodes/{node}` when calling '/nodes/mynode/status' requires permissions on | |
304 | `/nodes/mynode`, while the path `{path}` in a PUT request to `/access/acl` | |
305 | refers to the method's `path` parameter. | |
306 | ||
307 | Some examples are: | |
308 | ||
309 | * `/nodes/{node}`: Access to {pve} server machines | |
310 | * `/vms`: Covers all VMs | |
311 | * `/vms/{vmid}`: Access to specific VMs | |
312 | * `/storage/{storeid}`: Access to a storages | |
7d48940b | 313 | * `/pool/{poolname}`: Access to VMs part of a <<pveum_pools,pool>> |
b8eeec52 WB |
314 | * `/access/groups`: Group administration |
315 | * `/access/realms/{realmid}`: Administrative access to realms | |
316 | ||
317 | ||
3c8533f2 DM |
318 | Inheritance |
319 | ^^^^^^^^^^^ | |
320 | ||
5eba0743 | 321 | As mentioned earlier, object paths form a file system like tree, and |
3c8533f2 DM |
322 | permissions can be inherited down that tree (the propagate flag is set |
323 | by default). We use the following inheritance rules: | |
324 | ||
74936daf WB |
325 | * Permissions for individual users always replace group permissions. |
326 | * Permissions for groups apply when the user is member of that group. | |
327 | * Permissions replace the ones inherited from an upper level. | |
3c8533f2 | 328 | |
5eba0743 | 329 | |
80c0adcb | 330 | [[pveum_pools]] |
3c8533f2 DM |
331 | Pools |
332 | ~~~~~ | |
333 | ||
334 | Pools can be used to group a set of virtual machines and data | |
8c1189b6 | 335 | stores. You can then simply set permissions on pools (`/pool/{poolid}`), |
3c8533f2 DM |
336 | which are inherited to all pool members. This is a great way simplify |
337 | access control. | |
338 | ||
74936daf WB |
339 | |
340 | What permission do I need? | |
341 | ~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
342 | ||
343 | The required API permissions are documented for each individual | |
344 | method, and can be found at http://pve.proxmox.com/pve-docs/api-viewer/ | |
345 | ||
346 | The permissions are specified as a list which can be interpreted as a | |
347 | tree of logic and access-check functions: | |
348 | ||
349 | `["and", <subtests>...]` and `["or", <subtests>...]`:: | |
350 | Each(`and`) or any(`or`) further element in the current list has to be true. | |
351 | ||
352 | `["perm", <path>, [ <privileges>... ], <options>...]`:: | |
7d48940b DM |
353 | The `path` is a templated parameter (see |
354 | <<pveum_templated_paths,Objects and Paths>>). All (or , if the `any` | |
355 | option is used, any) of the listed | |
74936daf WB |
356 | privileges must be allowed on the specified path. If a `require-param` |
357 | option is specified, then its specified parameter is required even if the | |
358 | API call's schema otherwise lists it as being optional. | |
359 | ||
360 | `["userid-group", [ <privileges>... ], <options>...]`:: | |
361 | The callermust have any of the listed privileges on `/access/groups`. In | |
362 | addition there are two possible checks depending on whether the | |
363 | `groups_param` option is set: | |
364 | + | |
365 | * `groups_param` is set: The API call has a non-optional `groups` parameter | |
366 | and the caller must have any of the listed privileges on all of the listed | |
367 | groups. | |
368 | * `groups_param` is not set: The user passed via the `userid` parameter | |
369 | must exist and be part of a group on which the caller has any of the listed | |
370 | privileges (via the `/access/groups/<group>` path). | |
371 | ||
372 | `["userid-param", "self"]`:: | |
373 | The value provided for the API call's `userid` parameter must refer to the | |
374 | user performing the action. (Usually in conjunction with `or`, to allow | |
375 | users to perform an action on themselves even if they don't have elevated | |
376 | privileges.) | |
377 | ||
378 | `["userid-param", "Realm.AllocateUser"]`:: | |
379 | The user needs `Realm.AllocateUser` access to `/access/realm/<realm>`, with | |
380 | `<realm>` refering to the realm of the user passed via the `userid` | |
381 | parameter. Note that the user does not need to exist in order to be | |
382 | associated with a realm, since user IDs are passed in the form of | |
383 | `<username>@<realm>`. | |
384 | ||
385 | `["perm-modify", <path>]`:: | |
7d48940b DM |
386 | The `path` is a templated parameter (see |
387 | <<pveum_templated_paths,Objects and Paths>>). The user needs either the | |
388 | `Permissions.Modify` privilege, or, | |
74936daf WB |
389 | depending on the path, the following privileges as a possible substitute: |
390 | + | |
391 | * `/storage/...`: additionally requires 'Datastore.Allocate` | |
392 | * `/vms/...`: additionally requires 'VM.Allocate` | |
393 | * `/pool/...`: additionally requires 'Pool.Allocate` | |
394 | + | |
395 | If the path is empty, `Permission.Modify` on `/access` is required. | |
396 | ||
3c8533f2 DM |
397 | Command Line Tool |
398 | ----------------- | |
399 | ||
400 | Most users will simply use the GUI to manage users. But there is also | |
8c1189b6 | 401 | a full featured command line tool called `pveum` (short for ``**P**roxmox |
4f6e7e05 WB |
402 | **VE** **U**ser **M**anager''). Please note that all Proxmox VE command |
403 | line tools are wrappers around the API, so you can also access those | |
404 | function through the REST API. | |
3c8533f2 DM |
405 | |
406 | Here are some simple usage examples. To show help type: | |
407 | ||
408 | [source,bash] | |
409 | pveum | |
410 | ||
411 | or (to show detailed help about a specific command) | |
412 | ||
413 | [source,bash] | |
414 | pveum help useradd | |
415 | ||
416 | Create a new user: | |
417 | ||
418 | [source,bash] | |
419 | pveum useradd testuser@pve -comment "Just a test" | |
420 | ||
421 | Set or Change the password (not all realms support that): | |
422 | ||
423 | [source,bash] | |
424 | pveum passwd testuser@pve | |
425 | ||
426 | Disable a user: | |
427 | ||
428 | [source,bash] | |
429 | pveum usermod testuser@pve -enable 0 | |
430 | ||
431 | Create a new group: | |
432 | ||
433 | [source,bash] | |
434 | pveum groupadd testgroup | |
435 | ||
436 | Create a new role: | |
437 | ||
438 | [source,bash] | |
439 | pveum roleadd PVE_Power-only -privs "VM.PowerMgmt VM.Console" | |
440 | ||
441 | ||
442 | Real World Examples | |
443 | ------------------- | |
444 | ||
5eba0743 | 445 | |
3c8533f2 DM |
446 | Administrator Group |
447 | ~~~~~~~~~~~~~~~~~~~ | |
448 | ||
449 | One of the most wanted features was the ability to define a group of | |
5eba0743 | 450 | users with full administrator rights (without using the root account). |
3c8533f2 DM |
451 | |
452 | Define the group: | |
453 | ||
454 | [source,bash] | |
455 | pveum groupadd admin -comment "System Administrators" | |
456 | ||
457 | Then add the permission: | |
458 | ||
459 | [source,bash] | |
460 | pveum aclmod / -group admin -role Administrator | |
461 | ||
462 | You can finally add users to the new 'admin' group: | |
463 | ||
464 | [source,bash] | |
465 | pveum usermod testuser@pve -group admin | |
466 | ||
467 | ||
468 | Auditors | |
469 | ~~~~~~~~ | |
470 | ||
471 | You can give read only access to users by assigning the `PVEAuditor` | |
472 | role to users or groups. | |
473 | ||
8c1189b6 | 474 | Example1: Allow user `joe@pve` to see everything |
3c8533f2 DM |
475 | |
476 | [source,bash] | |
477 | pveum aclmod / -user joe@pve -role PVEAuditor | |
478 | ||
8c1189b6 | 479 | Example1: Allow user `joe@pve` to see all virtual machines |
3c8533f2 DM |
480 | |
481 | [source,bash] | |
482 | pveum aclmod /vms -user joe@pve -role PVEAuditor | |
483 | ||
5eba0743 | 484 | |
3c8533f2 DM |
485 | Delegate User Management |
486 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
487 | ||
8c1189b6 | 488 | If you want to delegate user managenent to user `joe@pve` you can do |
3c8533f2 DM |
489 | that with: |
490 | ||
491 | [source,bash] | |
492 | pveum aclmod /access -user joe@pve -role PVEUserAdmin | |
493 | ||
8c1189b6 | 494 | User `joe@pve` can now add and remove users, change passwords and |
3c8533f2 DM |
495 | other user attributes. This is a very powerful role, and you most |
496 | likely want to limit that to selected realms and groups. The following | |
8c1189b6 FG |
497 | example allows `joe@pve` to modify users within realm `pve` if they |
498 | are members of group `customers`: | |
3c8533f2 DM |
499 | |
500 | [source,bash] | |
501 | pveum aclmod /access/realm/pve -user joe@pve -role PVEUserAdmin | |
502 | pveum aclmod /access/groups/customers -user joe@pve -role PVEUserAdmin | |
503 | ||
0abc65b0 | 504 | NOTE: The user is able to add other users, but only if they are |
8c1189b6 FG |
505 | members of group `customers` and within realm `pve`. |
506 | ||
3c8533f2 DM |
507 | |
508 | Pools | |
509 | ~~~~~ | |
510 | ||
511 | An enterprise is usually structured into several smaller departments, | |
512 | and it is common that you want to assign resources to them and | |
513 | delegate management tasks. A pool is simply a set of virtual machines | |
514 | and data stores. You can create pools on the GUI. After that you can | |
515 | add resources to the pool (VMs, Storage). | |
516 | ||
517 | You can also assign permissions to the pool. Those permissions are | |
518 | inherited to all pool members. | |
519 | ||
520 | Lets assume you have a software development department, so we first | |
521 | create a group | |
522 | ||
523 | [source,bash] | |
524 | pveum groupadd developers -comment "Our software developers" | |
525 | ||
526 | Now we create a new user which is a member of that group | |
527 | ||
528 | [source,bash] | |
529 | pveum useradd developer1@pve -group developers -password | |
530 | ||
0abc65b0 | 531 | NOTE: The -password parameter will prompt you for a password |
3c8533f2 | 532 | |
8c1189b6 | 533 | I assume we already created a pool called ``dev-pool'' on the GUI. So we can now assign permission to that pool: |
3c8533f2 DM |
534 | |
535 | [source,bash] | |
536 | pveum aclmod /pool/dev-pool/ -group developers -role PVEAdmin | |
537 | ||
538 | Our software developers can now administrate the resources assigned to | |
539 | that pool. | |
540 | ||
541 | ||
542 | ifdef::manvolnum[] | |
543 | include::pve-copyright.adoc[] | |
544 | endif::manvolnum[] | |
545 |