Every piece of work in AIUS Light lives in a project, inside one organisation. A project brings together the people who work on it, the work AIUS does for them and what that work produces. Each part has its own rule for who can see it, so sharing a project never hands over anyone’s computer, connections or budget. To see a project’s structure and its figures in one place, open the project, choose Project actions (the … button), then Project structure and stats. Activity links to the same page. Every count on it is limited to what you can open yourself.

The parts of a project

Members

A project is either private (only the people given access by name) or open to the organisation (its members reach it through their organisation role). Organisation owners and admins manage every project open to the organisation, but reach a private project only when someone gives them access, as with private channels in Slack. People from outside the organisation join as guests. They see the current content and can download it; they do not see who else in the organisation takes part, or the project’s history and Activity.

AIUS

AIUS is a member of every project and organisation. It works only for the person who asks it, on that person’s computer, with that person’s access and connections, and never more. What it does is recorded under that person.

Computers

Work runs on the computer of the person who asks, in a folder linked to the project. A computer always belongs to its owner: being in a project never gives anyone else access to it. The structure page lists your own computers with a folder linked to the project; organisation owners and admins also get a link to the organisation’s Computers.

Connections

Connections (Slack, Gmail, Notion, a database…) are set up by each person in AIUS on their own computer; Connections in AIUS Light lists yours across your computers. The project stores none. When an Editor continues a shared conversation, it uses their own connections, never the author’s.

Conversations

A conversation belongs to the person who started it and is private until they share it with the project. Everyone with access can read a shared conversation. Editors and Managers can continue it: Download to continue, then run aius import <file> in the project’s folder. It becomes their own conversation, runs on their computer and is charged like any of their work. The author’s conversation is unchanged.

Folders and files

The project’s files, each with its revisions: what AIUS publishes and, depending on the organisation’s File sync setting (AIUS’s work, Append or Mirror), what a linked folder syncs. The structure page groups them by top-level folder.

Outputs

Reports, the decks made from them, analytical models and published sessions. Viewers see the current revision; Editors and Managers also see earlier ones.

Activity

Who worked in the project’s conversations, the model requests they made and what those cost, over 7, 30 or 90 days. Activity is for Editors and Managers in the organisation. Organisation owners and admins find the same figures for the whole organisation under Organisation → Usage and Activity.

Access and audit

Every grant, invitation, public link and sharing change is recorded, and stays recorded after it is undone. Reading is not recorded. Managers and organisation owners and admins read the log under Share project → Access changes. What Aius may do without asking, which files sync and which models and providers run are set in the organisation’s Permissions & security tab. A project can only be stricter than its organisation.

Organisation figures

Organisation owners and admins see the same parts summed over every project on the organisation’s Overview (content, usage, computers and growth), Usage and Activity. The structure page links there instead of repeating them.