User Agreements
Maintain the texts shown on the login and agreement pages — the User Agreement, Privacy Policy and so on — with support for multiple languages and versions. Menu: System Management → Basic Data → User Agreements.
When no agreement content is configured, the agreement page shows an empty state and login is unaffected; for a compliant launch, publish the current-language version of both agreements first.
Two-Level Structure
Agreement (definition) → version (content):
Fields of an agreement: name, display name, agreement type (user agreement / privacy policy, etc.), client type (which client it is shown on), default language, whether it is the default agreement.
Agreement-level actions:
| Action | Description |
|---|---|
| Set / unset as default | When multiple agreements of the same type exist, the default agreement is the one shown to users |
| Copy to another client | Copies the agreement together with the currently effective version of each language to the target client (for keeping a separate copy on the admin panel and the merchant panel) |
| Delete | Deletes the agreement together with all its versions; requires confirmation |
Versions hang under an agreement, with one version line maintained per language. List columns: version number, version label, title, language, status, effective time, change notes.
Version State Machine
draft ──publish──> published ──archive──> archived
│ │
└── delete └── copy as draft / archive- Publish: once a draft is published it takes effect externally; the previously published version of the same language is archived automatically — each agreement has exactly one effective version per language at any time;
- New drafts inherit automatically: a new draft loads the previous version's content of the same language by default; publish it after editing and it becomes the new version — no need to write from scratch;
- Switching languages: if the draft is unmodified, the previous version of the target language loads automatically; if it has been modified, confirmation is requested before overwriting;
- The editor reminds you of unsaved content before closing, preventing accidental loss of a draft.
Why version management matters
Agreement changes keep a complete history (when each version was published, what the change notes say), which can be cited directly in compliance audits.
What the User Sees
- Login page: the checkbox "I have read and agree to the User Agreement and Privacy Policy" at the bottom, with links that open the agreement pages; the checkbox state is remembered on the device, so the next login skips checking it again;
- Agreement page: shows the currently published version for that language (title, content, version label, effective time);
- After a new version is published: users who already gave consent are not forced to confirm again — when renewed consent is required, announce the change and let users review it themselves.
Related Links
- Announcements — the channel for announcing new agreement versions
- Admin Panel Overview — overview of the system management area