Anonimatum 1.6.0 — Public API, onboarding, Anonimatum-scoped members, page packs and per-user queue

Version 1.6.0 is a product leap: Anonimatum is no longer only a web app — it is also a product API for your workflows, with per-organisation onboarding, automatic plan activation after Stripe checkout, team management scoped to Anonimatum (invites, deactivation and reactivation without affecting other Politeia services for the same user), extra page packs and a background queue that processes one document at a time per user while allowing parallelism across users. Release date: 2026-09-01.

Overview: what changes in 1.6.0

If you come from 1.5.0 (native Word/Office, fixed PDF viewer, single minimal frontend), 1.6.0 builds on top with the SaaS product layer — signup, payment, quota, team and integrations. The thread: same quota and limits in the SPA and via API key, with multi-tenant isolation per group.

• API keys bound to Auth user + Anonimatum group: same quota as the web app.
• Integrations via `X-API-Key` header (plus SPA JWT) on `/api/public/` and `/api/pdf/`.
• Configurable onboarding: Home teaser, slug page, completion tracking.
• Stripe checkout: monthly/annual plans; plan activates on the payer’s group after charge.
• Anonimatum-scoped members: `rolesProducto: ['anonimatum']`, branded emails, setup at app.anonimatum.com.
• One user, one Anonimatum group (409 if already in another).
• Page packs 2k / 6k / 17k with card or SEPA.
• Queue: one `PROCESSING` document per user; parallel across users.

Public API and integrations

Anonimatum 1.6.0 exposes a product API surface documented in Swagger/OpenAPI (`public-api` and `product-api`). Keys are created from Intranet, linked to the Anonimatum group, and masked in listings. User/group context is unified for JWT (SPA) or API key auth.

X-API-Key header and Gateway

• Integrations send `X-API-Key` alongside the SPA JWT flow.
• Routes: `/api/public/` and `/api/pdf/` through the Politeia Gateway.
• Angular library: `provideAnonimatum({ baseUrl, apiKey })` for embed or automation.
• Technical docs for endpoints, Gateway and API-key security best practices.

Onboarding and signup per organisation

Each organisation can have its own welcome journey. Admins enable group onboarding and pick the welcome/signup page (configurable slug, e.g. `af-tax-legal`). Home shows a teaser to review the plan and complete onboarding.

Onboarding page

• Shows prices, page quotas, documentation and checkout link.
• Includes sample PDFs to validate redaction before payment.
• Demo video series: Tutorial 1 — Interface is live on YouTube as the first embedded episode.
• Downloadable user manual from the same page.

Plan activation and deactivation (Stripe)

Checkout uses Stripe with monthly or annual billing. After successful payment, the plan activates automatically on the group tied to the paying email. If the subscription is cancelled or payment stops, the group has no plan (quota 0) until restored; purchased page packs are kept on renew.

Members, Anonimatum scope and branded emails

From `/anonimo/perfil`, company admins invite with email, first name and surnames, deactivate and reactivate members. The 1.6.0 highlight is product scope: activation grants Anonimatum access only, not other Politeia products.

rolesProducto and SPA setup

• Invite payload includes `rolesProducto: ['anonimatum']`.
• `setupPasswordFrontendBaseUrl` points to the SPA (e.g. `https://app.anonimatum.com`).
• Email templates: `anonimatum_setup_password`, reactivation and deactivation with Anonimatum branding.
• Deactivation/reactivation uses `productScope=anonimatum` so other Auth services stay intact.

Extra page packs

Beyond monthly plan quota, buy extra packs from the quota counter (Home or sidebar): 2,000, 6,000 or 17,000 pages. Pay by card or SEPA via Stripe Checkout; success returns to `/anonimo/compra-exito`. The group pool consumes pages uniformly (plan + packs).

Per-user background queue

The queue processes documents in the background: one PROCESSING document per user, but multiple users in parallel (configurable global cap). Large teams do not block each other; each person gets a predictable flow.

1.6.0 capability summary