AIEUSAccess levels and defaults
What is open by default, what is closed, and who can grant access?
In a module, members read a few shared areas by default, admins read everything, and other files and folders stay shut until an admin grants a person one of three access levels. Keep in mind: Each person's own folder is open to them without a grant, and a bot working under its own account may read the introduction note at the top of it. Grants cover files and folders only; conversations and other database records follow their own rules.
In AIEUS, a module is a space with its own members, files and admins. Your personal folder in the module, including your Cortex (your own knowledge notes), opens only to you and the module's admins. Keep in mind: A bot answering you reads with your permissions. By default, a bot working under its own account can read only the introduction note at the top of your folder, not your Cortex. An admin can give that account more access. An admin can give other people access to parts of your folder.
Some areas are open to every signed-in member by design. They are the module's shared Cortex, its shared tools and how-to guides, and every bot's folder. A bot's folder includes what that bot keeps in its notes. Keep in mind: By default, members can read the shared Cortex but not change it. Admins can take away the default access to the shared tools and guides. Any member can read everything in a bot's folder and, unless an admin restricts it, change it.
Everything else stays closed until an admin gives a person access to a file or folder. Examples include other members' folders and team or project folders. That access can let them see that it exists, read it, or change it. Keep in mind: Only an admin can grant access. Writing 'shared with' in a note changes nothing. The lowest level shows a file's existence, name and descriptive details, but not its abstract (short summary) or contents.
Search, saved views and links between files obey the same rules. Each person finds and sees only the files they are allowed to see, even in a view someone shared. Keep in mind: A link between two files shows to anyone who can see both, even at the lowest level. It reveals neither file's contents. Searching by meaning covers only files you can read in full.
Unless a module is deliberately built to share data with outsiders, signed-out visitors cannot read your files, conversations or account. Public pages exist only if an admin puts them live. Unless the module is deliberately built that way, a public page shows only what is written into it. Keep in mind: Page code is never secret, so never put private text or keys in it. If a module lets outsiders sign up, those accounts can read what is open to every signed-in account. This includes the shared Cortex, bot folders and the account list. They cannot read private folders unless they are granted access.
Admins can read everything in their module. That includes every personal folder, account detail and bot conversation, and the module's stored secrets. It also includes a log of what you wrote, asked or searched through the module's tools. So treat everything in the module as visible to admins. Keep in mind: Nobody can read your password, admins included. The log hides passwords and keys it recognizes, not every secret. An admin of a parent module becomes an admin of a nested module when they first enter it. This does not happen if they already have an account there. Your instance's host (the person or company that installs and runs the AIEUS system your module is on) can reach the data. Your hosting agreement, not the software, limits that.
The module's audit log records each tool call made through MCP (Model Context Protocol) by a bot or a connected app: who, which tool, when, the outcome, the request and a short result. No account can edit or delete an entry directly, admins included. Keep in mind: Opening, editing or deleting files in the Web App is not recorded there. Only a few Web App actions are, such as rebuilding the Web App, pack actions, and creating or deleting modules. An admin can lift the protection by overriding the log's permissions and reapplying the module's database setup. AIEUS removes no entries while the module exists and has no setting for how long they are kept. Deleting a child module, which its parent's admin can do, removes its whole log. The host, with database access outside AIEUS's permissions, is not bound by this protection.
Partial: Everyone in a conversation can read its messages, and so can admins. This applies to bot conversations, one-to-one chats and channels shared with chosen people and bots. It includes private file content a bot quotes, since the bot uses the asker's permissions. Keep in mind: Pick a conversation's audience before discussing private material. A bot's behind-the-scenes steps stay visible only to the asker and admins. Members cannot delete messages. Shared conversations may not be live everywhere yet. Older bot chats, even continued ones, stay visible only to the sender and admins.