Early access by invitation
Orkyo Cloud moves to invitation-only access for design partners, and the login screen finally says why a sign-in was refused instead of looping.
Invitation-only early access
Orkyo Cloud is now open to invited design partners rather than to anyone who signs up. An identity that has not been invited is refused when it tries to link an account, and account creation answers plainly that no invitation exists.
Nothing was removed to do this. Self-registration became a setting that each edition declares for itself, so the same code serves both an open and an invitation-only product.
The login screen tells you what happened
Refused sign-ins used to end in a loop. The browser still held a valid Keycloak session, so “try signing in again” signed you straight back in and refused you again, with nothing on screen explaining why.
The failure reason now reaches the login screen and stays there.
Orkyo Community is unaffected
Community never sets the flag and keeps provisioning accounts on first sign-in exactly as before. This release changes who can create an account on Orkyo Cloud, and nothing about self-hosted installations.
Since this release
Version 0.15 repaired the requests importer, which had been mapping its columns to the wrong field names and silently rejecting every row, and taught the spreadsheet import to read the published capacity-planning template.