Directory
The people and groups your workspace owns — identities, addresses, and the customer each belongs to
The Directory is the roster of everyone your agents talk to or about — the people and groups your workspace owns, and the environments (end-customers) they belong to. It's the tenant-level source of identity: who someone is, which addresses reach them, and how agents should treat them.
Elsewhere in the docs and the API these records are called participants — the umbrella term for a person or a group. The Directory is where you manage them; Agent Network wires them to triggers and channels, and Applications grant them roles.
Mental model
The Directory holds two things:
| Tab | What it holds |
|---|---|
| Contacts | Every identity your agents reach — people (a customer, a teammate) and groups (a Telegram group, a Slack channel that acts as one addressable identity). Filter the list by kind. |
| Environments | The end-customers those contacts belong to. See Environments. |
People and groups share one tab because they are the same kind of record — both are participants, differing only in whether the identity is one human or a shared thread. Which one a contact is shows in its Type, and the kind filter narrows the list when you want just one.
People
Each person is one identity, described by:
- Type — the audience axis: Customer (someone you support) or Team member (internal staff, eligible to act as an escalation operator). Unclassified until you set it.
- Environment — the end-customer this person belongs to, or Unaffiliated. See Environments.
- Addresses — the provider handles that reach them: a Telegram chat, a Slack user, a phone number. One person can carry several.
- Linked accounts — external profiles (GitHub, Jira, …) used only to correlate a person's activity across products. Reference links only — never used to route messages.
The person detail
Open a person to manage four tabs:
- Profile — Profile details (a bio and contact preferences agents use when they describe, consult, or hand off to this person) and Placeholders (what a pinned tool parameter would fill in for this person, and which would fail the tool call; click Show to load them). Roster roles aren't on the profile; edit them from an Application's People → Roster roles.
- Identity & reach — Addresses (the channels this person sends and receives on, with health) and Linked accounts.
- Applications — which Applications this person has a role in.
- Activity — conversations observed through this person's addresses.
You can Test send a message to verify an address, and Pause a person to ignore their inbound and suppress outbound dispatch.
Adding people
| Action | What it does |
|---|---|
| Add person | Create a new identity by hand — a name and one or more addresses. |
| Add collaborator | Add an existing Fruxon user (a teammate with a login) to the Directory. |
| Import | Bulk-add identities from a CSV file. |
| Sync customers | Bulk-import an integration's contacts into the Directory. Appears only when an integration declares the directory-source capability, and runs a dry-run first. |
"Add collaborator" adds a teammate who signs in to Fruxon. Workspace access — who can view or administer an Application — is a separate concept, configured under an Application's Collaborators. See Applications.
Groups
A group is a shared thread treated as one addressable identity — a Telegram group or a Slack channel that many people post in, but that an agent reaches as a single participant. Groups live in the Contacts list alongside people; filter by Groups to see only them. They carry addresses and can be granted roles in an Application exactly like a person.
A Directory group is a channel, not a grouping of accounts. The chain or holding above an end-customer is an environment's group — a different idea, covered under Environments.
Environments
Environments live on their own tab and are documented in full on the Environments page. In short: an environment is the end-customer a contact belongs to — the unit you enroll an agent to serve, and the tag that splits cost and analytics per customer.