Loading
The full documentation site lives at docs.stampify.app and lands with the public marketing release. Until then, this page is the canonical landing for what's documented and where it lives.
Five-minute walkthrough from admin consent to a live signature in Outlook. Covers what to expect on the M365 / Google admin-consent screen.
Exact scopes Stampify requests on each vendor, and what we never request. Includes guidance for security teams reviewing the consent screen.
The brand palette / template split. CSS variables, Mustache merge fields, draft vs published, per-team templates.
Manual vs automatic sync, group-based selection, license assignment, suspending and deleting users.
How the add-ins call the render endpoint, the identity-token handshake, what they can and cannot read.
Server-side render endpoint reference. Vendor identity tokens, response shape, caching headers, error codes.
Pick the vendor your tenant runs on. The admin-consent flow lists every scope before you approve. Stampify never asks for mailbox, files, or calendar scopes; if you see one on the consent screen, stop and report it.
A template is HTML + Mustache fields + optional CSS variable overrides. The brand palette (5 colors, 1 font) sits one level up and is referenced as CSS variables (--primary, --secondary, etc). Drafts don't affect rendered signatures; publishing bumps the template version.
Sync mode: Disabled, Manual, or Automatic. Selection mode: All users, Specific groups, or Specific users. Each run writes a sync_runs row with counts and timestamps so you can audit what changed.
The add-ins are thin: they fetch a vendor-signed identity token, POST it to the render endpoint, and insert the returned HTML into the active compose body. They never read the message body, recipients, subject, or thread.
POST /api/render with the vendor identity token in the Authorization header. The endpoint resolves the user, merges template + global brand + per-user fields, and returns HTML with a short cache window. 401 on invalid token, 404 on unmapped user.
The full reference site ships with the public release. Until then, ask us directly, we'll write it up and link it here.
