Explicit consent
A user should understand which product is requesting a connection and what that connection is for.
FourPoint identity
FourAuth is the planned identity and authorization layer for connecting eligible FourPoint products. It is designed to make approved connections explicit without giving every product or account access to everything.
01 / DESIGN PRINCIPLES
A user should understand which product is requesting a connection and what that connection is for.
Each connected product should receive only the access required for its approved task.
Users should be able to review and revoke product connections when the real account system is implemented.
02 / PRODUCT CONNECTIONS
The first planned connection is between FourConvert and FourPrint. A user will be able to authorize FourConvert to provide a converted PDF to the FourPrint workflow. FourAuth is not required to download the FourPrint installer, and connecting products must not bypass their own permission checks.
The connection is not live yet. We still need to agree on the token scopes, return flow, expiry and revocation behavior, and the exact file-handling boundaries before implementation.
Read the connection flow03 / STATUS
FourAuth is currently a product plan and website page. There is no production identity provider, shared session, authorization server, or live product connection behind this page yet. The upcoming backend design will define those boundaries before any credentials or database tables are created.
04 / FOURAUTH ENTERPRISE
FourAuth Enterprise is planned for businesses, academic institutions and organisations. Enterprise registration asks for the enterprise name, the responsible head's first and last name, email address and password. Existing enterprise users will have a separate sign-in page.
05 / ACCOUNT EXPERIENCE
These pages show the proposed FourAuth account experience. They are interface previews only; account creation, sign-in, email verification and password recovery will require the real authentication backend.