Modules and updates

How do modules nest and update, and what crosses between them?

When a group needs a separate space rather than a shared folder, use a child module (submodule). It keeps its own files, database, accounts, permissions, AI providers, settings and bots. Keep in mind: A few things reach across modules. One installation-wide backup, set up in Root (the top module), covers every module. People in the parent module see each child's name and icon, but nothing inside it. Your name, email and time zone follow you into any child you enter.

Only a parent's administrators can create a child module. A new child module starts with no users of its own. The parent's administrators enter it as administrators. Members of the parent enter as members, unless the parent is Root. In both cases, the first visit creates their account in the child. Keep in mind: Root members who are not administrators need an account made for them in the child. You must have set your own password in the module you come from. Later role changes do not carry across. Your files, folder permissions and personal notes never carry across.

A module's administrators can rename it at any time. Its web address, though, is set from the name given at creation and never changes. That keeps bookmarks, links and connected apps working. Keep in mind: This applies to modules below Root. Root's address is the installation's own address. No feature changes an address or moves a module under a different parent. Deleting a module is permanent. There is no recycle bin.

When AIEUS is updated, files you never touched move forward to the new version. Any file you changed stays as you left it. If the update changed that file too, it is flagged for review. That way, your customizations survive. Keep in mind: In a child module, an update does not change the data structure or the Web App (AIEUS's browser interface) on its own. Those changes wait until the module's administrator applies them and rebuilds the Web App. If an update fails before it switches over, the previous software keeps running. However, a failed data-structure change is not undone automatically. A finished update can usually be rolled back to the previous software. Even then, the update's data changes stay unless the whole installation is restored from a backup.