AIEUSAccounts and sign-in
How do people get in, stay signed in and get cut off?
Each module keeps its own admin and member accounts, made by an admin or on first entry from a module above, and rechecks the account on every request. Keep in mind: From Root, only its admins get an account on first entry; other Root members must be added by an admin of the module below. Anyone entering from above must first have set their own password in that higher module. A module can also build a sign-up that lets outsiders make their own accounts. The instance's host makes the first Root admin, with database access outside AIEUS's own permissions.
Every account is either an admin or a member. An admin has full authority in that one module. A member can use their own folder and folders shared with them, and can read shared reference material. Members can also create bots (AI assistants) and connect AI apps such as Claude. Keep in mind: When an admin of a parent module first enters one of its child modules (modules created beneath it), they get an admin account there. The child's own admins can change that account.
Admins add and remove people, share folders, connect AI providers (the services that supply AI models) and create child modules. They can read, change and delete every file, including each person's personal folder. Keep in mind: Your instance's host (the person or company that installs and runs your AIEUS installation) is outside the module's accounts. What the host can reach is a hosting matter, not a module permission.
There are no email invitations. An admin creates the account, sees a random temporary password once, and passes it on privately. The newcomer gets a personal folder and sees nothing else private until granted access. Keep in mind: People cannot sign themselves up unless a module is built with its own sign-up for outsiders.
People sign in with their email and password for that module. At first sign-in, they must replace the temporary password with one of their own. The new password must be at least 8 characters and different from the temporary one. Keep in mind: The built-in sign-in is email and password only, with no second step such as a phone code or security key, and no Google, Microsoft or other single sign-on. There is no self-service reset for a forgotten password and no reset email. An admin issues a new temporary password instead.
Because there is no self-service reset, an admin who forgets their password needs another admin of that module, or an admin of a module above entering it for the first time, to issue a temporary one. Keep in mind: While still signed in somewhere, an admin can reset their own password or add a second admin. Once signed out, if no other admin can step in, as with the only admin of the top module, nobody inside AIEUS can reset it; recovery then rests with the instance's host, and no recovery procedure is documented as installed.
Not offered: AIEUS does not limit or lock out repeated wrong password attempts.
A sign-in stays active as long as it is used at least once every 30 days. But every action checks the account afresh. So disabling someone or resetting their password cuts them off at their next action. Keep in mind: Signing out ends only that browser's session, not other devices or connected apps. There is no list of active sessions to end. To cut off everything at once, an admin resets the password, or you change your own.
An admin can disable an account, which blocks sign-in but keeps its files and folder permissions. An admin can also delete an account for good, which keeps its files but not its permissions. AIEUS refuses to disable, demote or delete the last enabled admin. Keep in mind: A deleted account's files stay for an admin to handle. Re-enabling a disabled account can bring back sessions that had not yet expired. A password reset ends them for good.