The project designer, publishing pipeline or domain workflow received a material implementation update. Request, session, browser or abuse-protection handling received a material implementation update. The billing, checkout, payout or recurring-pay workflow received a material implementation update. Sign-in, passkey or account-verification handling received a material implementation update.
What users should notice
• A project remains attached to the same owner and project record from editing through publication. • The change strengthens the protection boundary without changing legitimate account permissions or product access. • Customers should see clearer progression through funding, onboarding and payment state instead of being sent between disconnected screens. • The affected account flow now uses the same server-side session and verification boundary as the rest of Ident.ink.
How it works
• Publishing state is resolved on the server and access remains checked against project membership before changes are accepted. • Security controls remain layered and server-enforced; public release notes never include rules that would help bypass them. • Sensitive payment details remain with the payment processor; Ident.ink stores only the references and operational state required for the workflow. • Authentication changes remain scoped to verified challenges, protected cookies and explicit account ownership checks.
Affected product areas
Administration, Account and platform security, Website and interface
Published on Discord by Ident.ink Bot.