By default, the Portail ZAPP address (“/”) sends a signed-out visitor to the sign-in page, and a signed-in user to their dashboard. Two settings of the Configuration screen (/configuration, administrators) let you choose other pages.
The two settings
| Setting | Purpose | Default value |
|---|---|---|
App:Home:AnonymousPath |
page served to a signed-out visitor who opens “/” (for example a public presentation page) | empty: sign-in page |
App:Home:AuthenticatedPath |
page served to a signed-in user who opens “/”, and right after signing in when no specific page was requested | empty: dashboard |
The application logo and name, at the top of the pages, link to “/”: they follow these settings.
Input rules
- Enter an address of the application, starting with a single “/”: for example
/portalor/welcome. An address of another site (https://…,//…) is refused when saving. - To restore the default behavior, enter
/. - If the address matches no page of the application, the default behavior applies: no visitor lands on an error.
- For signed-out visitors, the chosen page must be available without signing in. If it requires signing in, the sign-in page is shown instead, as before.
If your home page contains the sign-in form
A public home page can contain the sign-in form, and even the forgotten password form. Two settings of the Application category then send the Portail ZAPP links there:
| Setting | Links concerned | Default value |
|---|---|---|
App:Auth:SignInPath |
"Sign in" and "Back to sign in" (forgotten password, registration, address confirmation, header of public pages), link in the registration approval email, return after a password reset | empty: sign-in page |
App:Auth:ForgotPasswordPath |
"Forgot your password?" of the sign-in form | empty: "Forgot password" page |
Same input rules as above: an address of the application, for example /welcome or /welcome#password. When a session expires, or after a sign-in error, the full sign-in page is always shown: it is the page that explains what happened.
Links in the header of public pages
Public pages (knowledge base, site pages) have a header with the Support, Knowledge base and Sign in links. The KnowledgeBase:PublicHeader:Links setting, also in the Application category, adds others, between "Knowledge base" and "Sign in". It takes a list, for example:
[{"url":"/licences/mine","labelKey":"portal.public.nav.licences"}]
url: an address of the application (/…) or of anhttps://site;labelKey: the translation key of the label, to create in Translations for each language;- 8 links at most. Enter
[]to remove them all.
A badly written list is refused when saving, with a message that explains the expected format.
Instances already installed
These settings appear automatically in the Application category after the update, with an empty value: nothing changes until you modify them.