Every project belongs to an organisation, and every account starts with one.

Your personal organisation

When you register, AIUS creates an organisation that you own, named after your email address, for example Personal (ana.lopez). You can create projects and publish to it straight away, rename it, and invite people into it. It is always yours: it can’t be deleted or given to someone else.
The organisation page for Personal (ana.lopez): the owner role, the member list, the shared budget with no cap and recent usage

Where you work

One of your organisations is the one you work in: models from the terminal run on its budget, and new projects start there. It is your personal organisation until you switch:
  • in the terminal, open /organisation, pick the organisation and choose Switch to this organisation (or run aius platform organisation <id>);
  • on the web, open the organisation’s page and choose Make it my default.
The choice belongs to your account, so the terminal and the web follow it. If you leave that organisation, or become a viewer in it, you’re back in your personal organisation.

Shared organisations

For a team, choose New organisation in the sidebar, or Create an organisation… in the terminal’s /organisation, and give it a name. You own it. Nobody can join an organisation on their own: owners and admins invite people by email with a role, and they join when they accept.
RoleCan
OwnerEverything an admin can, and change roles, remove members, rename, transfer ownership and delete the organisation
AdminEverything a member can, invite people, manage the budget, and read the organisation’s activity and everyone’s usage
MemberCreate projects, publish reports and create share links
ViewerRead projects and reports
An invitation waits on the invited email address for 30 days. The person finds it on the Projects page after signing in, or registering, with that address, and the terminal tells them about it when it starts; they accept or decline in either place.
The AIUS Examples organisation page with its members, shared budget, recent usage and connectors

Managing organisations from the terminal

/organisation (also /org) lists invitations waiting for you and your organisations, with the one you work in marked. For each organisation you can switch to it, see its members, invite someone and pick their role, see and revoke pending invitations, and, depending on your role, change a member’s role, remove them, rename the organisation, transfer ownership, leave it or delete it. Its budget, usage and Google accounts open on the web.

Deleting an organisation

The owner of an organisation other than their personal one can delete it: on its page choose Delete, or use /organisation in the terminal, and type its name to confirm. Everyone loses access to its projects, pending invitations are cancelled and its Google accounts are disconnected. It can’t be undone.

Budget and model use

Model requests from the terminal are billed to the organisation you work in (see above). On the organisation page, the owner can set a shared budget: a cumulative cap in US dollars for requests billed to the organisation. Recent usage lists those requests with their recorded cost; members see their own.

Buying credit

Owners and administrators can choose Buy credit next to the shared budget, pick an amount and pay with Stripe. The credit is added to the organisation’s budget as soon as Stripe confirms the payment, and appears in the organisation’s activity as Credit added. When the budget runs out, model requests stop with a message to buy credit; the work already done is kept.