Publish the legal pages

MyZapp has two legal pages that can be read without signing in, from the footer of every page, including the sign-in page, the “Forgot password” page and the public pages of the knowledge base:

• Privacy (/Home/Privacy): the privacy policy. It must be readable before anyone signs in or creates an account. Without any setting, it shows a default text.
• Legal notice (/Home/Legal): the identity of the service publisher. Without any setting, this page does not exist and its link is not shown.

Their content is set on the Configuration screen (/configuration, administrators), Application category, without changing the application.

The settings

When both are set, the article wins over the address.

Show a knowledge base article

This is the recommended option: the text is written, translated and published like any other article, and each reader reads it in their own language.

1. Write the article in a knowledge base, translate it into the instance languages, then publish it.
2. Copy its identifier: the string of digits and letters after /articles/ in the address of the article edit screen.
3. Paste this identifier into Legal:PrivacyArticle or Legal:LegalArticle.

Good to know:

• Only this article becomes readable without signing in, with its screenshots, even if the knowledge base or the category is restricted to some groups. The rest of the knowledge base keeps its access rights, and so do the article's links to other articles.
• The article is shown in the reader's language. If it is not translated into that language, it is shown in the default language of its knowledge base.
• An article that is withdrawn or back to draft, or a disabled knowledge base, is no longer shown: “Privacy” falls back to the configured address or the default text, and “Legal notice” is no longer available.
• The source key of an article from the shipped documentation (for example module/file) is also accepted instead of the identifier.
• These two settings are not carried over when an instance is promoted to another one, because an article identifier differs from one instance to the next. Set them on each instance.

Send readers to an address

If your legal texts are published elsewhere, for example on your website, enter the address in Legal:PrivacyUrl or Legal:LegalUrl. The footer link stays the same; the page sends the reader to that address.

• The address starts with https:// (or http://), or it is an application address starting with a single “/”. Any other value is ignored.
• For a different address per language, add a key followed by the language code, for example Legal:PrivacyUrl:es. For a reader in Spanish, MyZapp tries Legal:PrivacyUrl:es, then Legal:PrivacyUrl.

The footer text

The footer of every page starts with a text set in App:Footer, Application category, for example the name of the company that publishes the service. Written between double curly braces, the word year is replaced by the current year: a "© year My Company" footer stays right every 1 January without any action.

• When empty, the footer shows "©", the year and the application name.
• For a different text per language, add a key followed by the language code, for example App:Footer:es. For a reader in Spanish, MyZapp tries App:Footer:es, then App:Footer.
• The text is shown as is: an HTML tag you type appears as text.
• This setting is carried over when an instance is promoted to another. Its per-language variant is not: set it on each instance.

Instances already installed

The legal page settings and App:Footer appear in the Application category after the update, with an empty value: “Privacy” keeps its default text and becomes readable without signing in, and “Legal notice” stays absent until you set it.