From 7bbbead063cbe74b344f36c6736c7ad60c78147d Mon Sep 17 00:00:00 2001
From: Étienne Loks
To access theses pages you have to identify you with an account with staff and superuser status.
-A superuser account is created at the initialization of the database. You can -create a new superuser account in the web interface (see the account -management section) or with the CLI:
+A superuser account is created at the initialization of the database.
+An Area is the base of your map. It defines:
+Areas are customizable directly on the web administration interface in +Chimere/Areas.
+As there is little chance that the default area is appropriate for you, you’ll +have to set at least one default area.
+Adding many area can be a mean to show your map in different flavors.
+If you are not the only administrator/moderator of this Chimère installation +you have to create and manage account for the other users.
+You can create a new superuser account with the CLI:
./manage.py createsuperuser
You probably want to define at least one default area. The configuration of -this area allow you to define the default zoom, welcome message, etc. of your -Chimère.
+User password can be changed with the CLI (useful if you have forgotten your +password):
+./manage.py changepassword username
If you are not the only administrator of this Chimère installation you have to create account for the other users. -Currently the process has to be done manualy.
-Simply click on the Add button near Users. Give a name and a default password (the user can change it on in own later). -Then complete the other pieces of information. -Check the case: Member of the staff (or this user will not be able to log to this administration site). -To simply give this user correct rights don’t add permission manualy but make this user member of a group. -Two default group are proposed: application administrator and moderator.
+Users are customizable directly on the web administration interface in +Auth/User.
+To create a new account, simply click on the Add button near Users. Give a name +and a default password (the user can change it on in own later).
+Then complete the other pieces of information.
+Check the case: Staff status (or this user will not be able to log to +the administration website).
+If this account is a new technical administrator, check Superuser status (this +user must be trustworthy!). Otherwise you’ll have to give permissions to this +new user. It is easier to don’t add permission manually but make this user +member of a group.
+Two type of default group are proposed: application administrator and moderator.
+Moderator are limited to an Area (they only see items that are inside the +bounding box). If a moderator manage many areas you’ll have to select many +groups.
Detail of rights for default user/groups:
| Task | -Application owner | +Technical administrator | Application administrator | Moderator |
|---|