|Documentation

Administering your instance

Reaching your portal's administration

Each instance has its own Lizmap administration, at your portal's address followed by /admin.php. That is where your portal's accounts, groups and rights are managed. The customer area gives you its address and the initial credentials; the screens themselves are Lizmap's, described in its documentation.

  1. Open Instances and click Manage on the instance's card.
  2. Click the Map portal card to expand it.
  3. Under Administrator access you will find the administration URL, the Login and the Password. The eye shows the password, the icon next to it copies it.
  4. Open opens the administration in a new tab. Sign in with these credentials.

The credentials shown are those set when the instance went live: the login admin and the password admin, the same for every instance. The instance page presents them as Initial password. As soon as you change this password in Lizmap, the page says Changed in Lizmap and stops showing the old one: it does not know the one you chose, since Lizmap keeps it only in an unreadable form. So keep your new password somewhere safe: the customer area can neither retrieve nor reset it. If you have lost it, write to support.

Change the password the first time you sign in. As long as it is admin, anyone who knows your portal's address can open its administration, see your restricted maps and change your rights.

What we administer, what you administer

An instance brings several programs together: the Lizmap portal, QGIS Server, the PostgreSQL/PostGIS database and a Redis cache. We install them and keep them running. You never have access to the server itself: your work goes through the customer area, the Lizmap administration and QGIS.

LizPack takes care ofYou take care of
Installing the instance and its programs.Preparing your projects in QGIS.
Running the services and recording their state, shown on the instance page: Active, Inactive or Degraded.Uploading your projects and data, through Files or the LizPack Publisher plugin.
Offering new versions of QGIS Server and Lizmap, and installing them when you click Update.Deciding when to update.
Serving the portal over HTTPS.Creating the portal's accounts and setting their rights in the Lizmap administration.
Checking every uploaded project: database connections, coordinate systems.Fixing the defects reported by that check and by the validator.
Measuring your files and your database against your plan.Staying within your plan's limits, or changing plan.

This split tells you where to look when something goes wrong. An empty, wrong or slow map almost always comes from the project: the project validator tells you before your visitors notice. An unreachable portal, or a service shown as Inactive or Degraded while the instance is started, is ours to fix: write to support.

Keep the originals of your projects and data. The customer area offers no way to go back to the previous version of a file that has been replaced or deleted.

LizPack accounts and portal accounts

Two directories coexist, and they do not talk to each other. An account in one opens nothing in the other.

Your LizPack account and your team

Your LizPack account opens the customer area: instances, databases, files, subscriptions. From the Pro plan, you invite colleagues there from Team. Each one gets a role (Administrator, Publisher, Viewer or Custom), permissions and the list of instances they can see. These accounts do not open your restricted maps.

A member with the View the instances permission sees the instance page as you do, database connection details included. Choose their permissions accordingly.

Your portal's accounts

They are created in the instance's Lizmap administration, not in the customer area. They are used to open maps that are not public and to allow online editing of data. Lizmap sorts them into groups and grants its rights per group, repository by repository.

A map is public when anonymous visitors are allowed to see its repository. To restrict it, remove that right in the Lizmap administration, or limit the project to certain groups from the Lizmap plugin in QGIS.

Securing your instance

An instance's security is shared between what we hold and what you decide.

What we hold

  • The portal and its administration are served over HTTPS: see certificates.
  • Each instance has its own services: its QGIS Server, its database and its file space are shared with no other customer.
  • Uploads refuse scripts and programs, as well as .sql, .env, .ini or .conf files.
  • An uploaded project can only connect to its own instance's database: if it targets another database, it is refused.

What depends on you

  • Changing the Lizmap administration password when the instance goes live.
  • Giving Lizmap administration only to the people who need it.
  • Removing people who have left, in the Lizmap administration as well as in Team.
  • Turning on Two-factor authentication for your LizPack account in Security: a six-digit code is then emailed to you at each sign-in.
  • Deciding what is public. An open project also publishes its data over WFS, attributes included.

The activity log records the actions taken from the customer area. If you think a password has leaked, change it at once: the Lizmap administration one in Lizmap, your LizPack account one with Change the password, in Security.