Worker
A worker is a seat that performs work. It has one of three kinds:
A person is one identity, and can hold more than one seat, for example an employee seat in one
organization and a contractor seat in another. Forge attributes work to the seat that did it and
shows the person once in people-facing lists. An agent has a seat but no person.
Because people and agents share the worker model, the same position can be staffed by either, the
same Trust Fabric rules apply to both, and cost rolls up the same way.
People
A person is the canonical human identity. Employment records (employee or contractor seats) are relationships of that person, not the person itself; a person without a current employment record stays visible as No employment record. Creating a person does not create a login, and an email that matches an existing person is never merged silently: you choose to link the records or keep them apart. Find people under Workforce → People. Each person’s profile shows their identity, employment records and allocation, and, with permission, their effective access.Agents
An agent is a worker whose seat is filled by an AI configuration: its instructions, its model routing tier, and the skills and tools it may use. Every agent has an agent kind:
The kind is stored as
agentType. It is not the agent’s autonomy level and not its model choice:
the agent’s tier field is its LLM routing tier (nano, low,
mid, high or frontier).
A worker agent works from a seat like anyone else. Its Ready to run checklist on the agent’s
Overview tab asks where it works: it has a worker, the worker sits in a position, the position
has a job role, and a team answers for the agent through that position. Personal agents are listed
only for platform administrators. Personal agents below explains how they act
for one person.
Find agents under Workforce → Agents, with Sessions, Config and Templates as tabs.
Pausing an agent stops new dispatches to it until it is unpaused.
Personal agents
A personal agent is one agent per person, created automatically. When Forge first sees a person, it creates their personal agent from the platform’s personal-agent template, opens a personal channel for them, and places the agent in it. The person signs in and the agent is already there. It is an ordinary agent with the Personal agent kind, owned by that person and dispatched the same way as any other agent. What it is for. The personal agent is the person’s default first contact in chat:- Report what is running for the person: their in-flight runs, approvals and notifications.
- Hand a task to the workforce by starting the right factory or workflow on the person’s behalf.
- Answer from the systems the person can reach, through capabilities.
- Consult a specialist agent when a question is outside its scope. The consultation is recorded.
- Trust Fabric evaluates the call against the person’s permissions. The agent cannot reach a system the person cannot.
- A run it starts is attributed to the person, and cost rolls up to the person’s team and department.
- Audit records name the person.
Org units
An org unit is one node in the organization tree: the company root, a department, a team, a capital partner or a customer organization. It is the scope at which access is granted. A role granted at an org unit applies there and in every unit beneath it. To decide whether a caller holds a permission on a record, Forge checks the caller’s grants at the platform and at the record’s org unit and each unit above it. Forge Console shows the tree under Workforce → Organization, and calls an org unit an organization in the role dialog. The API resource is/api/v3/org-units, and the permission keys are org:read and org:manage.
Several other workforce words describe people and where they work, not access scopes:
Positions
A position is a place in the tree, attached to one org unit. A person fills it, or an agent does when the position allows agent assignment. Enabling agent assignment does not assign an agent by itself. Assignments are dated, so the history of who held a position is kept. Manage positions under Workforce → Organization → Positions.Job roles
A job role describes the work that positions share: responsibilities, and for agent-staffed positions the instructions, skills and tool sets the agent uses. Several positions can carry the same job role. A job role is not a Trust Fabric role and grants no permission; if a worker cannot perform an action, check their access, not their job role. Manage job roles under Workforce → Organization → Job roles.Groups
A group is a set of people that spans the organization tree without changing anyone’s position or reporting line. Use one when work genuinely crosses the hierarchy. Group membership coordinates work; it does not grant permissions. Manage groups under Workforce → Organization → Groups.Pods
A pod is a team of people for delivery work. It has a name, a managing org unit, and dated Lead and Member memberships; a worker can belong to no pod, one pod or several. Pods can be assigned to customers and projects to model allocation and capacity. A pod is never an authorization scope. It does not change the org chart, anyone’s org unit membership or anyone’s access, and its managing org unit is organization metadata, not a grant. Manage pods under Workforce → Pods; reading them needsworkforce:read and changing them needs
workforce:manage.
Teams and factories
Departments and teams are org units, so they appear in the organization tree and can receive role grants. A factory is a production unit for sustained project work: a manager agent coordinates a team of human and agent workers with its own channels and budget. See Factories.Identity
Identity is how a caller becomes a worker Forge can authorize and attribute.- A person signed in to Forge Console, a hosted MCP host signed in as that person, or a script using that person’s personal key acts as that person.
- An External App acts as itself, never as a person.
- An external account, such as a Slack user, a GitHub login or a directory record, links to a person through an identity claim. Forge records how each claim was verified: an OAuth sign-in, an email match, an administrator’s assignment or directory (SCIM) provisioning.
Where you see it
- Forge Console
- HTTP API
- MCP
- Workforce → Organization: the tree, with Structure, Positions, Job roles, Groups and Settings tabs.
- Workforce → People and Workforce → Agents.
- Workforce → Pods and Workforce → Planning.
- Workforce → Integrity: workforce data problems to review.
- Platform → Identity: external accounts that did not map to a person.
Related
Organization
Browse and change the organization tree.
People
Create people, link identities and review access.
Agents
Check an agent is ready to run, pause it or hand off its work.
Positions
Create seats and allow agent assignment.
Job roles
Describe the work that positions share.
Groups
Group people across the tree.
Pods
Staff delivery teams and assign them to customers.
Define an agent
Give an agent its instructions, skills and tools.

