Docs
Person
Someone in a tenant's organization — a member of the tenant, or someone its agents work with — placed on the chart with their title and the person they report to. A person is a place in the organization, not a login (that is the account) and not a right to change the tenant (that is the membership).
Has: one tenant · a name · an email, one per tenant, compared without capitals · a title and a department (both may be empty) · who they report to: another person of the tenant, or the organization itself · the account with that email, when there is one · the people their agents know them as (agent-accounts with the same account) · where the record comes from (the Hub today; a directory later) and that directory's id for them (empty today) · a state. A tenant has many; deleting the tenant deletes them. A person who leaves is kept, so history still says who managed what.
Who is a person
Every member of a tenant is a person in its organization, made when they are invited (MEMBER-BY-INVITE). When this landed, every member who existed became one. An operator's automatic place in every tenant is not an invitation, so it makes no person.
PERSON-EVERY-MEMBERBeing a person in the organization gives nobody a place in the tenant: it does not let them sign in to the Hub or change anything. An owner or admin can add someone who is not a member, so the chart can show a colleague who only works with agents in Slack.
e.g. an admin adds Ana as a person → she is on the chart; the Members list is unchanged and she cannot open the Hub.
PERSON-NOT-MEMBERSHIPA person is linked to the account with their email, and through it to that account's chat ids and agent-accounts, so the chart, the Members list and each agent's People tab speak of the same human (ACCOUNT-CHAT-ID).
PERSON-LINKED-BY-EMAIL
Who they report to
A person reports to one other person of the same tenant, or directly to the organization, the top of the chart. Several people may sit directly under the organization, as founders or managing directors do; nobody is assumed to be a chief. Never to an agent.
e.g. Ben's manager set to Ana → saved; Ben's manager set to Nova (an agent) → refused, nothing written.
e.g. four founders, each reporting to the organization → all four side by side under it.
PERSON-REPORTS-TO-A-PERSONA change that would make someone their own manager, directly or up the chain, is refused and nothing is written.
e.g. Ana reports to Ben; setting Ben to report to Ana → refused.
PERSON-NO-CYCLEAn owner, an admin or an operator edits a person's name, title, department and manager in the Hub; a member sees them with every control disabled (MEMBER-WHO-MAY-CHANGE). The API checks the same right.
PERSON-EDITED-BY-ADMINS
Leaving
An owner or admin marks a person as left. They stay on record but leave the chart; the people who reported to them now report to whoever the leaver reported to — a person, or the organization; and the agents they managed go up the same way (ORG-AGENTS-GO-UP). Removing someone's membership is not leaving: they stay in the organization unless they are marked as left.
e.g. Ana (manager Carla) leaves → Ben, who reported to Ana, now reports to Carla, and Ana's agent Nova is managed by Carla.
e.g. Ana's membership removed, not marked left → she is still on the chart, still Nova's manager.
PERSON-LEAVESA person who left can be brought back; they return with no reports and no agents, and nothing is handed back to them on its own.
PERSON-COMES-BACK