Hexis Files

Inviting people

• An invite gives people a way to sign in, with or without single sign-on. Without single sign-on the Invite dialog asks for a starting password, given to every new account and to an existing one that has none; an account with its own password keeps it. With single sign-on a password is an option. Each result row says how that person signs in, and the message to forward never contains the password.
• One way to create accounts. User accounts' Add account form is replaced by an "Invite new users" row that opens the same Invite dialog; Manage access offers an Invite action for an address with no account, where no single sign-on lets them in otherwise.
• Everyone sees Invite. Someone who is not an admin is shown the admins, each with an Email button, to ask one.
• Distributions can tell invited people themselves. An invite now runs the account-invited listeners a deployment registers, and the dialog says "Emailed" for anyone a listener reached.

Accounts

• The owner can never be locked out. The owner can't be switched off, and their account can be deleted only where they can still sign in with a password the server holds. Another admin can no longer set the owner's password.
• A switch-off that meets another change still being saved answers "try again in a moment" instead of failing.

Pages

• New page only where you can write. The Get set up step and the command menu create the page in a Knowledge folder you may write, and are not offered to someone who may write none.

Branding

• Distributions can name the login page's legal links and the maker link in the app menu.

Upgrading

The image ghcr.io/bevel-software/hexis:0.28.0 and the npm packages @bevel-software/platform-* 0.28.0.