One shared graph beats five private ones. When you invite colleagues, the organization graph becomes the team's memory: one answer for everyone, and you decide who sees what.
Create your team
From the team page in app.fivo.ai, create your team and invite members by email. Each invitation arrives by email, and the invitee signs in with their own account. The team page shows who is active, who is pending, how many licences are in use and how many are free.
During the 14-day trial you can invite as many people as you like. See Plans, trial and billing.
Roles
An organization has one Owner and members with one of three roles.
- Owner: pays for the plan, connects and manages the Brain, brings sources in with organization scope, and can transfer ownership or delete the team. The owner reads everything that came from organization sources.
- Admin: manages members and can confirm or reject proposed identity matches. An admin cannot connect the Brain or claim organization sources; that stays with the owner.
- Member: uses Fivo fully within what they are allowed to see.
- Viewer: read access.
Whatever the role, the graph shows each person only what they could see at the source. A role never widens access to a private channel or someone else's inbox. See Permissions: what your Brain can see.
What happens to a member's graph
Before joining a team, a person has a personal graph. When they join an organization, their personal graph is superseded by the organization's: they now view and contribute to the shared graph, and their personal sources (email, for example) keep feeding a personal layer that only they see. Fivo merges both when they ask a question.
When someone leaves the team, their membership is marked as ended in the graph. Their past participation in meetings and conversations is kept as history; they stop being resolved as a member from then on and lose access to the organization graph.
Spaces
A space (shown as a Channel in parts of the app) is a shared area inside your organization for a sub-team: a client account team, a department, a project. You give it a name, invite its members and add reports to it.
Every report added to a space is visible to the space's members immediately, and so are the facts the Brain extracted from it. This is the easiest way to share meetings with a group instead of person by person.
Spaces have their own membership, so a report in the "Acme" space is visible to the Acme team and not to the rest of the company, while the organization owner still sees everything.
Members in your AI
Over MCP your assistant can list the organization's members and the members of each space, with links to their entity in the graph. That makes questions like "who worked with Acme before I took it over?" or "who is on the Platform squad?" answerable without opening Fivo.
Identities across tools
Members are known to the graph from the directory, so the "Ada" on a call and the "[email protected]" in email are one person from the start. For handles the directory does not know (a GitHub username, a Slack id), Fivo proposes matches that an owner or admin confirms. Each person can also declare their own handles in their Fivo settings. An external person who matches nobody gets their own node as a contact.
Managing the team
From the team page you can resend or cancel invitations, change roles, remove members, add licences, rename the team, transfer ownership or leave. Removing a member frees their licence.
Next
Connect sources with organization scope so the whole team benefits: Connect your tools.
- team
- spaces
- roles
- members