Inventory Accounts
Accounts
Inventory › Accounts lists people, not logins. One person appears once, and every sighting of them is folded into that row: a tool signed in as them, a machine they use, a connection that lists them as a member.
A person appears once one of three things happens:
- a tool reports who it is signed in as;
- a machine records who is using it;
- a connection syncs its members.
Who can do it
| You want to | You need | Roles that hold it |
|---|---|---|
| Read the list, a person and their history | connections:read (View connections) | All six built-in roles |
| Run an action on a person's record at a connected platform | connections:manage (Manage connections) | Owner, Admin, Fleet operator |
| Change Corporate domains | fleet:manage (Manage the fleet) | Owner, Admin, Fleet operator |
Read the list
Each row is one person. It shows their address or login, a line of facts, when they were last seen, and a mark for each place they were seen: a connector's logo, an AI tool, or the agent.
Open a row to read the person in the panel beside the list.
| Control | What it does |
|---|---|
| Search | "Search by address or login". |
| Grouping | Flat, By domain or By enterprise. Groups are headed by the domain (No domain when the login is not an address) or by Enterprise, Personal or Unknown. |
| Add filter | Filters, listed below. |
| View | Chooses what each row's second line shows, under On each row: Domain, Enterprise, Presences, Machines. |
| Corporate domains | Opens the list of domains your company owns. |
| Filter | Values |
|---|---|
| Seen on | Tool on a machine, Agent, or a connector by name. |
| Discovered by | Tool on a machine, Connector, Agent. |
| Enterprise | Enterprise, Personal, Unknown. |
| Corporate address | Yes, No. |
The list loads 50 people at a time as you scroll.
What Enterprise means
A vendor can say whether an account is an enterprise account or a personal one. The panel shows what each sighting said. If no vendor has, the person reads Unknown: "No vendor has said whether this person is enterprise or personal."
Corporate address is a separate mark. It is Yes when the address is on one of your Corporate domains. It is computed on the server.
Set the corporate domains
- Choose Corporate domains above the list.
- Add each domain you own, for example
northwind.com, in Domains. - Choose Save domains.
Addresses on these domains and their subdomains are corporate; every other
domain is flagged. With nothing set, only well-known consumer domains are
flagged. A pasted @northwind.com is stored as northwind.com. The list
holds domains, not addresses, and refuses an entry that looks like an address.
A person's page
| Tab | Holds |
|---|---|
| Overview | Identity key, First seen, Last seen, Last resolved, Presences, Machines, and the enterprise verdicts. |
| Presences | Each sighting, with What this sighting carried. A sighting from a connection can offer What can be done here. |
| Machines | The machines that reported this person. |
| History | An Action, a Record, an Interaction or an Issue. |
| Issues | Issues about records this person holds. |
An identity key is an Address, a GitHub login or an OS user. A person you can see through a connection has a status of Active, Suspended, Invited or Disappeared.
Run an action on a presence
Some connectors let you act on the record behind a sighting, such as a member of a platform. Under What can be done here:
- Open the person and choose Presences.
- Choose Run on the action. An action that cannot be undone shows "I understand this cannot be undone." and its button carries the action's own name.
- After it runs the page says "label ran." Choose See it on the connection to read the attempt.
Only a connection's sighting has actions. A tool and an agent sighting are observations: there is nothing to run on them. See Connections.
When it goes wrong
| You see | What it means |
|---|---|
| "This workspace's people could not be read." | The list failed. It is shown instead of an empty table. |
| "Could not load more people." | A later page failed. The rows already shown are still true. |
| "Connector names are unavailable, so people are listed by connector id." | The names could not be read; the people are correct. |
| "The corporate domain list could not be read." | Corporate domains is disabled until it can be read. The marks on the rows are unaffected. |
| "You can view this workspace's tools but not configure them. Changing corporate domains needs the fleet:manage grant." | You hold read access only. |
| "The domains could not be saved." | The save failed. |
| "This person could not be read." | The panel could not open the person. |
| "This person's history could not be read." | The History tab failed. |
| "This person's Issues could not be read." | The Issues tab failed. |
| "That action did not run." | The platform refused or could not be reached. |
| "This connection has not been checked yet." | The connection has not run its Check, so no action is offered. |
Empty states: No people yet with the three ways a person appears above; "No people match these filters."; Nothing recorded for this person yet ("Actions, record changes, interactions and Issues land here."); No Issues for this person ("One appears when a connection's rule matches a record this person holds."); "No machine has reported this person."; and "Nothing has reported this person yet — no connection, no tool and no machine."
With the API
People, their presences and history are in Accounts. Running an action on a presence is in Inventory.