Choose Connect
The user starts in FourConvert or FourPrint and sees which product is requesting access.
FourAuth / Connection guide
Connect products
with clear consent.
This is the proposed connection flow for FourConvert and FourPrint. It documents the intended experience, not a live authentication feature.
PLANNED FLOW · NOT IMPLEMENTEDPROPOSED FLOW
From request to revocation.
Review the request
FourAuth will identify the requesting product and show the specific permission being requested.
Approve or cancel
The user explicitly approves the connection or returns without granting access.
Use a limited connection
The approved product receives a short-lived, scoped authorization. It does not receive a general account password.
Revoke when needed
The planned account settings will let the user review active product connections and revoke access.
BOUNDARIES
What this connection must not do.
No shared passwords
Products should never exchange or store each other's user passwords.
No blanket access
A successful sign-in alone must not grant access to a business, printer, document, or admin action.
No false privacy claims
File transfer, retention, token scope, and deletion behavior must be tested before being described as guaranteed.
Next implementation dependency
Before building FourAuth, FourPoint must approve the database model, product registry, authorization scopes, session and token lifetimes, server-side secret handling, and the integration contract for FourConvert and FourPrint.
Back to FourAuth overview