SEAL and branding

01In a nutshell #sec_dbaaf8dc

Two settings decide what your documents and consoles carry of you: the certificate that signs the exported PDFs — without an active certificate, it is the platform's SEAL that signs — and your logo, your color, your font, applied everywhere.

02The signature of documents #sec_301a2dab

Settings › Document signature. Configure the signature of PDF documents for your subscription. Manage the certificates used to sign PDF exports.

What signs when you do nothing

The Default certificate block says it: The platform SEAL « … » signs your documents; it is valid until … Any report edition, any attestation projection exported as PDF bears this SEAL. It is a verifiable electronic signature — the Verify a signed document page of the workspace journey shows it — but it says REVIEWIT, not your organization.

If no SEAL is installed on the hosting, the screen says it too: your exported documents cannot be signed until you upload your own certificate.

Signing in your name

Document signature is activated with a switch, then Import a certificate: a .pfx file with its private key and password. The certificate appears with its name, its issuer, valid from … to …, and its status: Valid, Expiring soon, Expired, Inactive.

Set as default designates the one that signs. The counters at the top — Total certificates, Active certificates, Expiring soon, Expired — are the list to reread: an expired certificate no longer signs, and the exports fall back to the platform SEAL without anyone noticing in the moment.

A qualified certificate in the sense of eIDAS gives your PDFs a qualified signature; an internal certificate gives a verifiable, non-qualified signature. The difference is read in the verification verdict, and it is up to you to know which one your compliance requires.

What this does not change

The sign-off of reviewers and the attestations of REVIEWIT are not signed by this certificate: they are sealed by the platform's trust perimeter, and are verified offline by their own contract. This setting concerns the exported PDFs — report editions, readable projections.

03The branding #sec_1bb8ddf2

Settings › Customization › Branding. Your logo, your color and your font, applied to all workspaces and to the Review Manager. Each console takes the new values at the next page load.

The logo

SVG preferred · 2 MB max. Drag the file or Browse. And know where it goes: the logo also goes into campaign emails and certification folders. A reviewer who receives a reminder sees your logo; an auditor who opens a piece too.

The color

Only one — everything else follows. It lands on seven elements: application bar, active tab, gauge, main button, border and text of the secondary button, table links. The background, the cards and the content text never change.

The screen refuses an unreadable color: White text unreadable on this color. At least 4.5:1 is required. It can remain your brand color, but it cannot carry the application bar and the buttons. It then proposes the same hue, darkened. Accept it: the readability of the buttons is not a matter of taste.

No background color: the background of the consoles remains the neutral gray of REVIEWIT, so that the evidence is read everywhere in the same way. If you had a custom background before, the screen shows you before / after and confirms that logo, color and font are preserved.

The font, and the preview

A font among those proposed. Then Preview — Review Manager, as your reviewers will see it, in real components: the queue, a campaign, the buttons. What you see is what they will see.

Save: visible at the next page load. Reset REVIEWIT branding returns to the original charter.

04The rhythm #sec_98d0642e

05To remember #sec_9cff7b55

A certificate of yours signs your PDFs, otherwise the platform SEAL does it and says so. A logo, a readable color, a font — and never a background, so that the evidence is read the same everywhere. The two settings are seen outside the console: in emails and in pieces.