Differences

This shows you the differences between two versions of the page.

--- useradminpanel [2007/10/02 13:39] – morten
+++ useradminpanel [2010/05/01 21:58] (current) – old revision restored morten
@@ Line 37: / Line 37: @@
 **Note:** A new user will be given implicit membership to the groups "authenticated users" and "anonymous users". If you do not tweak on group membership, that will be his/hers set of rights. This also goes for users created with LDAP.
@@ Line 52: / Line 55: @@
 ^ Group ^Description ^ Comment |
-^ Anonymous users  |Unauthenticated users (not logged in) |Everyone are implicit members. Gives access to the home page, the traffic map, viewing (not composing) messages and maintenance |
+^ Anonymous users  |Unauthenticated users (not logged in) |Everyone are implicit members. Gives access to the home page, the traffic map, viewing (but not composing) messages and maintenance |
-^Authenticated users |Any authenticated user (logged in) |New users are implicit members. Gives in addition access to everything except the typical admin stuff: user admin, seed database, module delete, composing messages and maintenance setup   |
+^Authenticated users |Any authenticated user (logged in) |New users are implicit members. Gives in addition access to everything **except** the typical admin stuff: user admin, seed database, module delete, composing messages and maintenance setup   |
-^NAV Administrators |Full access to everything | This access is implicit, no privileges need to be defined for NAV Administrators |
+^NAV Administrators |Full access to everything | This access is implicit, no privileges need to be defined for NAV Administrators. As a member you have access to everything in the web interface. |
 ^ SMS |Allowed to receive SMS alerts | |
@@ Line 60: / Line 63: @@
    * To modify an existing group, click on the group.
 In both cases you proceed to the "Group Details" tab
 ===== Group Details =====
-Use this to create new groups or edit existing. Each group must have
+Use this to create new groups or edit existing. Each group must have:
-   * A unique and preferably intuitive name
+   * A unique and preferably intuitive name.
-   * A description that explains what group membership this group authorizes
+   * A description that explains what group membership this group authorizes.
+The actual definition of the group is shown in the Privileges section.
+   * To grant new privileges to the group, select the privilege type and then enter your target. If you misspelled your target or something, revoke it and create a new one (you can not edit a privilege). You can add as many privileges as you like to a group.
-The actual definition of the group is shown in the Privileges section
-   * To grant new privileges to the group, select the privilege type and then enter your target. If you misspelled your target or something, revoke it and create a new one. You can add as many privileges as you like to a group.
@@ Line 84: / Line 91: @@
 ^web_access | Controls what part of the web system a user has access to. Based on regular expression matching against actual NAV URLs. |
 ^alert_by | Takes only one valid target: 'sms'. A user is not allowed to receive sms messages from NAV unless he has the "alert_by for sms" on his privilege list. |
+**Note:** Confusingly a third privilege is possible to choose; report_access. Since this privilege has no implementation, we will remove the option in a later NAV version (and reintroduce it when/if we actually implement support).
 To see examples of how you can use the web_access privilege, take a look at the definitions of the predefined group