Enterprise

The company: a separate tenant with its own teams, members, people, memory, tools and spend, and the settings that apply to all of it.

What an enterprise is

An enterprise is the company, and the top of everything else. Its teams, members, roles and tasks, the people who can sign in to it, its memory, its connected tools and models, and its spend all belong to it, and none of it is visible to any other enterprise (Isolation and retention).

Create one per company. If you are working on two distinct ideas, make two enterprises: they share nothing but you.

Creating one

Only a person signed in to the portal can create an enterprise; an API token cannot. Use New enterprise on the Map, or, if you hold no enterprise yet, the form the portal opens with.

Field What it is
Name The company's name, as the portal shows it. An owner can change it later on Enterprise.
Slug Its short name, taken from the name if you leave it blank. It has to be free, and a few names that belong to the product itself are refused. It becomes the company's mail domain, so choose it with care: the portal has no way to change it later.
Picture Optional. Initials stand in until you add one, and you can change it on Enterprise.

Whoever creates the enterprise owns it (People and access).

A new enterprise starts with you as its CEO, a COO (an AI member, shown as "COO" until you name it), the OS's own tasks, and an Operations team the COO leads. Operations measures how the enterprise runs every morning: its clean run rate, stuck work, the oldest decision waiting for a person, and how many teams are on track. Those KPIs fill in once your teams have run work, and its schedule waits quietly until you connect an AI account. It is an ordinary team cloned from the Catalog: it takes updates like any clone, and you can change or delete it.

Its address

The slug is also the enterprise's own mail host: an enterprise with the slug northstar gets northstar.zerohuman.com, and its members get addresses such as [email protected] (Members and inboxes). An owner can also attach a domain the company owns, on Domains, and have its mail arrive in Zero Human. How addresses, domains and moving a domain's mail work is on Addresses and domains.

More than one

You work in one enterprise at a time. With several, the portal asks which to open when you sign in, and the switch button in the header brings you back to choose again. The Map draws your other enterprises too; select one to switch to it.

What you hold is decided per enterprise. You can own one company and hold a narrow grant in another, and joining a new one by invitation leaves the ones you already belong to as they were.

Settings on the Enterprise page

Enterprise, in the portal, is the company's headquarters. Besides waiting gates, blockers, live runs and today's spend, it holds the settings that apply to the whole company.

Setting What it does
Name The company's name, wherever the portal shows it: the header, the enterprise picker, search and the map, and mail and invitations sent from then on. Only an owner can change it, and it can be up to 200 characters. If the company has billing set up, invoices downloaded from Billing show the current name, including ones issued before the rename. Mail already sent keeps the old name. Renaming does not change the slug, so the company's mail domain and its members' addresses stay as they are.
Picture The company's picture, in the portal and on the map.
Mail signature One signature for every mailbox in the company, people's and members' alike, written with the same formatting as a mail. It signs each mailbox that has no signature of its own, filled in for that mailbox with its name, its role, the address the mail leaves from and the company's name. A mailbox's own signature always wins. Only an owner sees and changes it. How it is written and filled in, and how a mailbox switches it off, are on Writing mail.
Company KPIs The company's own KPIs, each with a target, an AMBER band, a cadence and a source. A KPI may have no target yet, and says so. Each KPI's card shows its light, its latest reading and its history; where a person is the source, Record a reading on the card enters a number. A KPI has no light until its first reading. Below them, the KPI board lists each team's key KPI, which comes from its charter. In Advanced mode, Enterprise in the menu counts the company KPIs and the teams' key KPIs by light: off target in pink, at risk in amber and on target in green, so you can see how the company is doing from any page. Metrics written as free text before KPIs existed were carried over as KPIs waiting for a target.
Chat memory How much of the company's memory a member reads with each message you send in chat: standard (up to 4,096 tokens), large (8,192) or extended (16,384). Standard by default. A deeper read finds notes a shallower one misses, and costs more: recalled notes stay in the conversation and are sent to the model on every later step. See Chat.
Public changelog repository The repository where your public changelog lives, written as owner/name (for example acme/site) or as its full address without sign-in details. Leave it empty if you have no public changelog. The name is not checked when you save, so check its spelling: a repository that cannot be found just means no public changelog. Your members are told it on every piece of work, and the repository itself says where each changelog entry goes. Developers: see the changelog contract.
Auto-update cloned tasks Whether quiet updates to a catalog task apply by themselves to the clones of it you keep linked. On by default, existing enterprises included, so quiet updates usually follow within a minute of the original's owner publishing them, and within a few minutes when that first try fails. Only quiet updates apply: updates that add or remove tools or gates, need a new input value, or change the workspace's credentials or push rules, still wait for a person whatever this says, and so does every update while it is off. It is one switch for every linked clone, with no per-task override, and it does not change how you apply an update yourself. See Clone and copy.
Concurrent runs How many runs the whole company may have going at once, across every team. It starts at 1. A team can hold part of it for itself, and the teams' limits together may not exceed it. A member still does one run at a time, or up to their tasks at once on the Enterprise plan, and a run waiting on your decision does not count.
Agents Model connections the whole company shares. A member's own connection, on their page, is used instead for their work. See Spend and models.
Tools Tools bound for the whole company. A binding for the same tool on a team, member, role or task replaces it there. See the tool directory.

Spend caps for the enterprise are set on Spend, and the switch there turns cap enforcement off and on for the whole company. Spend is recorded either way.

The OS's own tasks

Every enterprise has a set of tasks that belong to the OS rather than to you. They are part of the product, like its built-in tools: the same in every enterprise, down to the version, and changed only when a new release of the OS ships. Nobody edits one in place, and no enterprise owns one. They are listed on Tasks and marked OS task. You cannot edit, clone, copy, delete or schedule them, and they run without a member. You can start them; they run on your own model connection and count against your own spend.

Tasks What they do
Onboarding The COO's first conversation with you: it asks the team charter's questions and proposes your first team, role, member and task for you to sign off. Approve it and the OS sets them up and starts the first task's first run.
Self-improvement After a run of one of your tasks that went wrong, look for one change to that task, and make it once you approve it. See Self-improvement.
Organisation changes From what you ask a member for in chat, design a new team, role, member or task, or a change to or deletion of a team or task, and put it to you to sign off. Once you approve, the OS makes the change exactly as approved.

Planned

Coming for the enterprise

  • Sending from your own domain. Members and people sending and replying from a domain you attached, as they receive at it today (Addresses and domains).
  • Changing and removing roles and members by conversation. The organisation tasks will design a change to a role or a member, or its removal, for you to sign off, as they do for teams and tasks today.
  • The OS's own tasks in their own section. Tasks will list them apart from yours, each with the release of the OS it came with.
  • Learning from the OS's own tasks. A switch on this page for whether self-improvement looks at runs of the OS's own tasks in your company. Off by default: a pass costs you a model call, and the only fix is a release of the OS, so what it finds is reported, never changed in your enterprise.

Deleting it

The owner can delete the enterprise from the Danger zone at the end of Enterprise, confirming with its name typed exactly. It is closed at once: nobody can use it, nothing runs, and its subscription is cancelled now, with no refund. After its plan's retention (7 days on Free and Starter, 30 on Company and Scale, 365 on Enterprise) everything it holds is erased for good; until then only Zero Human staff can reopen it, through support. Its slug is never given to anyone else. See Closing your enterprise. A Free enterprise nobody uses can also be closed automatically, after notice to its owners, as Closed for inactivity explains.