Publish your terms of use

01In a nutshell #sec_1cc6069c

Your terms of use are drafted in a draft, language by language, then published: acceptance will be requested before the next access, and each acceptance remains attached to the exact version that was read.

02Where #sec_7ed17f94

Settings › TOS & acceptance. Three tabs: Overview, Publications, Acceptances. Without publication, the screen says so: Create a draft, add its languages then publish: acceptance will be requested before the next access.

03What your users will see #sec_a45c6ac5

Before writing, look at what they will read. Preview shows the barrier as it stands in the way: Acceptance required — Read the TOS before continuing. Your organization requires your acceptance before normal access to REVIEWIT. With the version, the language presented, the account, and the button I accept and continue. Under the button: Your action and the version presented will be recorded as proof of acceptance.

It is a barrier, not a checkbox in a corner: a reviewer does not reach their queue until they have accepted.

04Drafting a draft #sec_81e9bb6c

Create a new version. Draft — no modification is visible to users before publication. Only one draft at a time: a draft already exists — resume it or delete it first.

Languages. One default language, mandatory: the publication cannot be published without content available in this language. Then Add a language for each variant. A user receives the variant of their language, or the default language.

The format, by language. Inline HTML or PDF — the format is specific to each language. A publication can therefore mix HTML and PDF. In HTML, the sanitized preview shows exactly what will be kept and displayed: what disappears during sanitization will not be in the TOS. In PDF, 10 MB max, one upload replaces the current file.

Save this language, language after language. The Languages card says which ones are ready.

05Publish #sec_1887c99d

Publishing... requires two things:

• Reacceptance: Mandatory — all those who had accepted a version

must accept this one — or Not required — only new users will see it. A form correction does not justify interrupting everyone again; a substantive change does.

• Nothing else: publication is immediate.

And a non-negotiable rule: a published version can no longer be modified. To correct the content or a translation, create a new version. The reason is in the Publications tab: old publications remain accessible to accurately restore the accepted content. An acceptance proves something only if that something no longer changes.

06Track acceptances #sec_7e29b7a1

Overview counts the current obligation: Up to date, To be accepted, Total — population: users who have accepted at least once. Someone who has never logged in is not listed; they will be intercepted on their first visit.

Acceptances lists by user their status, last acceptance, language, and version. Filterable, exportable to CSV: it's the piece you hand over when asked who accepted what.

07Renewal #sec_53d6cb50

Configure renewal activates a periodic reacceptance, from 1 to 120 months. Each user expires according to the date of their own last acceptance — not all on the same day. Disabled by default.

08Suspend obligation #sec_11c2cdfe

An incident, a version to be urgently withdrawn: Suspend obligation. During suspension, users are no longer intercepted and no acceptance is recorded. The history remains intact. Upon resumption, you will choose if a new acceptance is required. The confirmation message summarizes it: the barrier lets through.

09The cycle #sec_22734cd4

10To remember #sec_82cccda9

A draft, languages, a default language, then a publication that is no longer touched. The proof of acceptance holds because the accepted text does not move. Choose reacceptance based on the substance of the change, not by reflex.