Cloud platform settings

Cloud operators can manage the product identity shown by the Cloud cabinet under Operator console → Platform settings. The panel controls:

• the public and short-link domains;
• the public contact and abuse-report addresses;
• the Terms of Service and Privacy Policy links (by default the product’s published documents at https://mockarty.ru/legal/terms and https://mockarty.ru/legal/privacy; the cabinet also serves the same texts at its own /legal/terms and /legal/privacy);
• the sender address, reply-to address, and sender name used by Cloud mail;
• whether the cabinet shows the support contact.

The values are saved centrally and survive a Cloud restart. Review the contact address before opening the service to users: installations created from an earlier database image may still show the previous address. For a Mockarty-operated service, set the public contact to info@mockarty.ru in this panel; no rebuild is needed.

Saving requires a recent sign-in, current password, or 2FA code. The form uses an exact revision: if another operator saves first, reload the latest values and repeat the change. Every successful update is recorded in the Cloud audit chain and in immutable settings history.

The unauthenticated cabinet receives only the public domain, contact, legal-link, revision, and support-display fields. Outbound mail routing metadata is visible only to operators. Connector credentials and secret values are never returned by this API.

Changing the sender identity does not configure or validate outbound delivery. A successfully saved identity therefore does not prove that registration or recovery mail can be delivered.

Branding and regional defaults

The panel also carries the identity the cabinet and the sign-in page render, and
the deployment’s regional defaults:

• Product name — shown where the product names itself.
• Logo URL — an https:// URL on your public domain or a subdomain of it.
  Leave it empty to keep the mark the product ships with.
• Brand accent — a six-digit hex colour such as #2563eb. It tints the brand
  mark’s backdrop and nothing else. It deliberately does not paint text: a colour
  you choose cannot be checked against WCAG AA on both themes the way the shipped
  palette is, and a brand colour is not worth an unreadable heading.
• Default language — the language used for the interface and for letters to
  somebody who has not chosen one themselves. Cloud is published in Russian and
  English.
• Default time zone — an IANA time zone name such as Europe/Moscow.

These values belong to the same revisioned settings record as the domains and the
legal links: one save, one revision, one audit entry.

Revision history and rollback

Show history lists every recorded revision with the time and the operator who
made it. From that list you can:

• Compare with current — see exactly which fields a rollback would change,
  and what they would become, before performing it;
• Roll back to this — make that revision current again.

A rollback does not delete or rewrite anything. It writes the chosen revision’s
values as a new revision, so the history is append-only, the rollback is
auditable, and the rollback itself can be rolled back. Like any other change it
requires identity confirmation and an exact revision.

A rollback is validated exactly like a fresh save. If an older revision carries a
value the product no longer accepts — a retired domain, for instance — the
rollback is refused and names the field, rather than restoring a value the
product cannot honour.

Only operators can read the history. The public endpoint keeps returning the
public identity only: domains, contacts, legal links, branding, regional defaults
and the revision number.

System announcements

Under Operator console → Platform → System announcements, an operator can
schedule a notice for the Cloud cabinet, connected desktops, or both. Choose a
type, title, message, and start and end times, then select at least one place to
show it. The time fields use your device’s local time zone. Leave the plan and
region fields empty to address everyone; if you narrow either field, enter the
matching codes separated by commas. A link is optional, but needs both a label
and an http:// or https:// URL.

Publish announcement asks you to confirm your identity. The panel then
shows whether the notice is scheduled, currently showing, or ended. Withdraw
stops it early after confirmation. Both actions are recorded in the audit trail.
Cloud announcements do not publish a notice on a separate Mockarty installation;
that installation manages its own notices.

If you close a Cloud release or event notice in a connected Desktop while
offline, Desktop keeps the action and sends it when the Cloud connection
returns. Once sent, the same notice is hidden in your Cloud cabinet and on
your other connected devices after they refresh. A corrected notice can appear
again; maintenance and incident notices continue to appear while active.
Notices published by a separate Mockarty installation remain local to it.

Multiple Cloud replicas

Cloud runs more than one API replica. Each replica keeps a bounded snapshot of the
settings so a page render does not read the database, and PostgreSQL tells every
replica the moment a revision is written: a change saved on one replica is
visible on the others within a round trip, not after a timeout.

If a replica cannot listen for those notifications it falls back to refreshing on
a short interval, and the history panel says so instead of showing you a revision
list as if it were current. When the database is briefly unreachable a replica
keeps serving the last known good identity for a bounded time; past that bound it
reports the settings as unavailable rather than showing a value nobody can vouch
for.