Buildings, people and roles
A building brings machines and people together. Each person has a role in each building they belong to, and that role applies to every machine in that building.
Roles
| Role | What they can do |
|---|---|
| Owner | Everything, plus inviting people, changing roles, adding and revoking machines and changing the building’s settings. |
| Operator | Chat, queue, approve, start sessions, open previews, commit and push. |
| Viewer | Watch only: sees sessions and chats, but doesn’t send messages or approve. |
| Auditor (Enterprise) | Reads the audit log, reports and who saw what. Doesn’t see sessions or chats and can’t act. |
A building is never left without an owner: the last owner can’t demote themselves.
Building deliveries
On Team and Enterprise, what someone approves in a building project (the delivery card’s Approve) and what goes out through the Outbox is kept in the building, on the hub, without depending on the computer of whoever did it. So if someone leaves, the delivered work stays. Only the result goes up: the approved files (up to 25 MB each) and the sent content, never the conversation, drafts or anything not approved, and never secrets (.env, keys). There are 10 GB on Team and 100 GB on Enterprise; above that, the delivery is recorded without the copy. The owner and the auditor see everything; others see the projects they work on (what they approved and what was done on their computers). In the personal area and on the Personal plan, nothing goes up.
To browse: Deliveries, on the top bar (on a wide screen), or See the building deliveries in Settings → Buildings (also on a phone). Search by title, filter by project, label, type and period, and download the files (downloads go to the audit log). The owner sees the storage used. With a project chosen, the owner and operators give it up to 8 labels (the client, the department), to group deliveries without a client registry. Deliveries approved in a team are included too.
How it was done: in a building project, the delivery card shows, before Approve, the path to the result: the request and the tools used, in order ("Apollo · searched", "Canva · created the design"), without the conversation and without the data that went through the tools. Remove what doesn’t need to stay and approve: the path is kept with the delivery. In Deliveries, open How it was done on a delivery and tap Do it again this way: it opens a new conversation with the same path, and the agent first asks what changes, using your own accounts in the tools.
When someone leaves: in Settings → Buildings → People, Remove shows, before taking the person out, what they delivered (from the building’s vault, nothing read from their computer) and what’s open under their name: the teams they created, the spots and approvals in teams, the computers they look after (with their routines) and the tasks shown to the building. Pick who takes over in Hand over to (someone who operates in the building) and tap Hand over and offboard: all of it moves to that person, the leaver’s access is cut right away, and the deliveries stay in the building.
Building recipes: a path that works becomes the house way. In Deliveries, open How it was done on a delivery and tap Make it a building recipe (owner and operators), with a name like "Promo post". When the same path repeats three times, Fleetly suggests it. Recipes sit at the top of Deliveries: tap one and Do it this way. In the Command center, ask "how do we do promo posts here?": the Fleetly agent answers with the recipe and examples.
Building roles: in the editor of one of your library roles, Share with the building lets everyone in the building see and use it (it shows under From the building, with who created it). Only the creator and the building owner change it; others make their own copy to adjust it. Routines live on the building’s computers and move along with them when someone leaves.
Invite someone
- In Settings → Buildings, open the building and go to People → Invite someone. Type the name of the person to invite and pick the role. Optionally, add their email: the link goes by email too.
- Use Create invite (and Copy link, to send it however you like).
- Send the link. It’s valid for 24 hours and works once. The person signs in with their account (or creates one) and starts seeing the building; someone who already has an account just joins it.
Invites, roles and multiple buildings are part of the Team and Enterprise plans. On Team, you pay for owners and operators; viewers are free. See pricing.
Change roles, remove someone and leave
- The owner changes each person’s role in People, and removes someone with Remove.
- Anyone who isn’t an owner sees Leave organization on the card and stops seeing the building’s machines.
- All of this goes into the building’s audit log, which the owner sees in View audit log.
Create another building
In Settings → Buildings → New building, give it a name (a client’s, for example) and use Create building. It’s a separate building: only the people you invite see its machines. Then open the building and use Machines → Add machine.
What each person sees
A role applies to every machine in the building. In a building with two people, each one sees the sessions on the other’s machines; an operator can also act on them (send messages, approve, commit).
What protects personal work is folders: outside the folders the machine’s owner chose on the machine itself, nothing leaves it. On personal machines in a building with more people, set the folders.
- People in other buildings see nothing of your machines: for them, your sessions don’t exist.
- Fleetly doesn’t show system processes, only Claude Code, Codex, Antigravity and GitHub Copilot sessions.
- In the team view, owners and viewers see everyone’s numbers; operators see their own (see below).
Team view
In Report → Team (Team and Enterprise), per person in the building: sessions, time with agents working, time waiting for approval, time with an answer ready waiting for the person, tokens and commits made through the dashboard.
A session counts for whoever drove it most through the dashboard in the period (messages and queue). If nobody did, it counts for the machine’s owner (chosen in Settings → Buildings → Machines); with no owner set, it shows as "No owner".
Audit log
Sign-ins, messages, approvals, new sessions, queue, commits, pushes, previews, settings and machine changes are recorded with the person, the address and the time. The owner sees the building’s audit log; on Enterprise, it exports to CSV or JSON.
Didn’t find what you were looking for? Write to admin@fleetly.tools.