Workspaces and Teams
MeetLoyd organizes everything around a clear hierarchy that mirrors how a real company is structured — so your AI workforce is easy to reason about, secure, and scale.
| Level | What it is | Think of it as |
|---|---|---|
| Tenant | Your organization | The company |
| Workspace | An isolated project or department | A department or client engagement |
| Team | A group of agents working toward a shared goal | A squad with a clear purpose |
| Agent | An individual AI worker with a role and tools | An employee |
"Create a workspace for our EMEA sales org and a lead-qualification team in it." Loyd sets up the structure and asks only what it needs. Meet Loyd →
Workspaces — your top-level containers
A workspace keeps a body of work separate: its own agents, teams, data, and settings. Use one per department (Sales, Support, Finance), per client, or per major initiative.
Each workspace can carry a briefing — a short statement of its goals and context. Agents read the relevant parts of that briefing so they act with the right strategic direction, not in a vacuum.
Workspaces are also a natural boundary for governance and access: policies, integrations, and permissions can be scoped to a workspace, so the Finance workspace can be locked down tighter than the Marketing one.
Teams — agents with a shared purpose
A team is a set of agents that work together toward one goal — a "Customer Support" team, a "Sales Development" team, a "Compliance Monitoring" team. Within a team, agents have roles, report lines, and clear hand-off and escalation paths, so work flows to the right specialist automatically.
Teams are composable: you can build one from scratch, start from a ready-made template, or have Loyd assemble one from a description. When a team comes online, MeetLoyd runs a short start-up process that gives each agent an approved charter before it acts — see your first agent and composing teams.
How to structure yours
- One workspace per department or client. Keeps data, costs, and access cleanly separated.
- One team per outcome. A team should have a goal you can state in a sentence.
- Let specialization happen. Several focused agents beat one agent trying to do everything.
- A team of one is fine. Start small; grow the team as the work grows.