Agent profiles
Learn what an agent profile is, why your organization needs one, and how it controls the identity, compute, and behavior of Droid sessions that run on your organization's behalf.
An agent profile is a saved setup for running Droid on behalf of your organization instead of a single person. It defines how Droid behaves, which identity it runs as, and which computers it runs on. When a teammate delegates work from Slack, Linear, Jira, Microsoft Teams, or Google Chat, Factory starts the session from an agent profile, so the teammate does not choose a model, identity, or computer for each request.
Why use an agent profile
Without an agent profile, every shared request would need someone's personal credentials and a computer chosen by hand. An agent profile replaces that with one setup a Manager or Owner controls:
- Set it up once. Model, instructions, plugins, identity, and compute apply to every session the profile starts.
- Run work as the organization. Shared sessions run as the profile's service account, so sessions, computers, usage, and audit events belong to that account instead of whichever teammate asked.
- Control access in one place. Droid can use only the repositories, connectors, and API keys you grant the service account. A teammate's personal connections are never passed to a shared session.
- Keep behavior consistent. Custom instructions apply to every session, such as which tests to run, what a summary contains, or when to open a pull request.
What an agent profile contains
| Part | What it controls |
|---|---|
| Default model and Default reasoning level | The model sessions use unless a requester's personal delegation defaults override it and organization policy allows that. Auto Model uses Factory Router. |
| Custom instructions | Instructions added to every session the profile starts. |
| Plugins | Plugins installed in every session, in addition to plugins enabled organization-wide. A plugin disabled organization-wide stays disabled. |
| Identity | The service account sessions run as. Its Git credentials, connectors, API keys, and computers determine what Droid can reach. |
| Compute | Dynamic builds a fresh computer for each session from one organization Environment. Persistent schedules sessions onto a pool of computers owned by the service account. |
| Per machine parallel worker limit | For Persistent compute, how many sessions can run on each computer at once. The default is 3. |
| Access | Who in the organization the profile serves. |
The Org Default agent profile
Every eligible organization has a built-in agent profile named Org Default. It powers all shared work delegated from Slack, Linear, Jira, Microsoft Teams, and Google Chat.
When Factory sets up an eligible organization, it creates Org Default along with a service account and an Environment for it. Review those defaults before your team delegates work. If setup could not finish, the profile setup wizard asks you to choose an active identity and compute.
Org Default always serves everyone in the organization. You cannot rename or delete it. Restricting access to specific groups is coming soon.
Because one profile serves every delegation app, a change to Org Default affects Slack, Linear, Jira, Microsoft Teams, and Google Chat at the same time.
Agent profiles and service accounts
An agent profile and its service account do different jobs:
- The service account is who the work runs as. Repository access, Git credentials, connectors, API keys, and computer ownership belong to it. See service accounts.
- The agent profile is how the work runs: which service account to use, plus model, instructions, plugins, and compute.
Shared sessions run as the service account, not as the administrator who edited the profile. Give the service account its own access to every repository the work needs, including every repository in the profile's Environment. See repository access for the service account.
Individual plans and the Teams plan include one service account, reserved for Org Default. Business and Enterprise plans can create additional service accounts for other automation.
Which identity a request uses
The agent profile always supplies instructions and model defaults. Where the request comes from decides which identity and computer the session uses:
| Request | Runs as | Computer |
|---|---|---|
| Slack channel, Microsoft Teams channel, or Google Chat space mention | The profile's service account | The profile's compute |
| Linear or Jira issue | The profile's service account | The profile's compute |
| Slack or Google Chat direct message to Factory | The person sending the message, with their own Git credentials and connectors | A computer for that person built from the profile's Environment, or their DM delegation machine |
Personal delegation defaults let each requester choose a model and add their own instructions after the profile's instructions. They never change the identity a shared session runs as.
Choose compute
Use Dynamic unless the work needs something an Environment cannot provide. Each session gets its own computer built from the Environment, so there is no pool to size, keep online, or maintain. A profile uses one organization Environment; personal Environments are not eligible. See Run Droids on an Environment.
Choose Persistent when sessions need long-lived machines, your network, or specific hardware. The pool is every active computer the service account owns. Add Factory-managed Droid Computers, your own computers through Remote Control, or both.
Configure an agent profile
You need the Manager or Owner role.
- 1Open Settings → Delegations.
- 2Under Agent Profiles, select Edit on Org Default.
- 3Work through the profile's settings and select Finish to save.
For each setting, follow configure the Org Default agent profile.