Skip to content

Projects

Open it: Projects · second item in the console menu.

A project holds a team’s work: its agents, templates, flows, triggers, resources and canvases. Everything in A3T belongs to exactly one project, and the project decides who can see it and who can change it. A project is either personal (yours) or an organisation’s.

Projects, grouped by owner: the platform's, an organisation's, and their projects

Items lists your projects grouped by owner: your handle first, then your organisations, then the platform’s. The project picker in the top bar narrows every app to one project; the address then starts with /p/<project>/, so a link opens in the same project for whoever follows it.

Personal projectOrganisation project
OwnerYou, by your handleAn organisation you are a member of
Namespace<your-handle>-<name>, e.g. qa-operator-support<org>-<name>, e.g. acme-support
Who can create itAnyone with the Operator role or higherAn admin or member of that organisation
Who can see itYou and the members you addIts members, the organisation’s admins and security admins, and every member of the organisation unless it is private
Who can change itYou, and members with the owner or developer roleIts owners and developers, and the organisation’s admins
PrivateOnly you and its membersOnly its members and the organisation’s admins and security admins

Two projects belong to the platform: a3t (A3T’s own agents, flows and shared resources) and system (the core agent and A3T’s internals). Everyone can read them and clone from them; only a SuperAdmin can change them.

Add people on Access & policy › People. Type a name or email: everyone who can sign in is listed, including people who sign in through their organisation’s own identity provider (marked SSO).

A project's Access & policy: people, where it runs, who else can use it, rules

Project roleWhat they can do
ownerEverything, including members, rules, moving and deleting the project
developerBuild and run: agents, templates, flows, triggers, resources, canvases
operatorDeploy and run what is there; no authoring
viewerRead only

A person’s account role is the ceiling. Someone whose account is a Viewer stays read-only in every project, even if a project makes them an owner. Removing a member takes effect on their next request.

Access & policy › Who else can use it lets people outside the project read, clone and run what is in it, never change it.

ChoiceWho gets itHow they see it
Nobody else (default)Only the project’s own people—
Selected organisationsThe organisations you nameAs community items in their lists
All organisationsEveryone on the platformAs community items

The platform’s own projects share differently: what a3t shares appears as shared (to use or wire in) or training (examples to learn from and clone), and system shares only with a3t.

TabWhat it shows
OverviewIts description, owner, visibility, your role; counts of agents, flows, resources and deployments; runs today and failures; the latest runs
ContentsEvery agent, flow, template, resource, trigger and canvas in it, each with a link
EnvironmentsWhat runs where, and each environment’s variables (dev, staging, prod)
HealthIts deployments and the runs that failed in the last 24 hours
Access & policyPeople, where it runs, who else can use it, its rules
BillingWho pays and its budget. Sample data until billing is connected
SettingsDisplay name, description, private; move to an organisation; delete

A project's Environments: what runs where, and variables per environment

A variable has a value per environment. When a canvas deploys into an environment, its pods get that environment’s values. A secret variable names a Secret resource to read the value from; the secret itself is never stored in the project.

ChoiceMeaning
Shared runtimes (default)Any runtime the platform offers
Only its own runtimeOnly a runtime labelled a3t.io/project=<namespace> (an org project’s choice: a3t.io/org=<org>)

The three ready-made rules (only owners deploy to prod; destructive tools need an owner; agents remember per user) are saved with the project but not enforced yet. To enforce a rule today, a security admin writes a Cedar policy for the project in Security.

A project's Settings: name, description, private, move to an organisation, delete

ActionWhoWhat happens
Move to an organisationThe owner of a personal project, who is an admin of the target organisationThe namespace becomes <org>-<name>. Its flows, resources and triggers move with it, and references inside the project are rewritten. Preview lists anything outside the project that refers to it and would break. Run history stays under the old name
Change organisation—Not available yet: an organisation’s project can’t move to another organisation
Delete projectIts owner, or an admin of its organisationOnly when it is empty. Move or delete its agents, flows, resources and triggers first. Removes the project, its members and its rules; run history stays

The Support desk team at Acme starts in a personal project and moves to the organisation when it goes live:

  1. Ann makes the personal project ann-support and builds her help-desk agent there.
  2. She adds Sam as developer on Access & policy › People. Sam signs in with Acme’s own identity provider, so he is listed as SSO.
  3. When it is ready, Ann opens Settings › Move to an organisation, picks acme, checks Preview, and moves it. It is now acme-support; Acme’s admins can manage it and every Acme member can read it.
  4. To let Globex try the agent without changing it, Ann sets Who else can use it to Selected organisations: globex.