[{"data":1,"prerenderedAt":54},["ShallowReactive",2],{"$f11ivz8a24kb17":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"bridge":8,"html":10,"headings":11},"\u002Fdocs\u002Fcontrol\u002Fisolation","Isolation and retention","What stays inside your enterprise, what a model is and is not shown, how long run history is kept, and what closing an enterprise deletes.",null,false,[],"\u003Ch2 id=\"one-enterprise-one-tenant\">One enterprise, one tenant\u003C\u002Fh2>\n\u003Cp>Each enterprise is its own tenant. What it holds is visible only inside it:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>What\u003C\u002Fth>\n\u003Cth>Stays inside the enterprise\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Memory\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>A run and the API read only their own enterprise's memory. Another enterprise's notes are never loaded, whatever a request asks for.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Runs and executions\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Their inputs, logs, results, events and costs.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Credentials\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Model connections, tool connections, the webhook secret and API tokens. None can be read back once saved, in the portal or over the API: a new webhook secret or API token is shown once, when it is made.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Mail\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Each member's inbox. A run reads only its own member's mailbox.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Inside an enterprise, memory is shared. Teams, roles and tasks are labels on one memory, not private stores, so\nnever train a secret into it. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fmemory\">Memory\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>A task you clone or copy from \u003Cstrong>Catalog\u003C\u002Fstrong> brings its definition and nothing else: no credentials, no memory, no run\nhistory. See \u003Ca href=\"\u002Fdocs\u002Fwork\u002Ftasks#clone-and-copy\">Tasks\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"throwaway-run-environments\">Throwaway run environments\u003C\u002Fh2>\n\u003Cp>A run that works on files (a clone of a repository, tests, a build) does it in a\n\u003Ca href=\"\u002Fdocs\u002Ftools\u002Fworkspaces\">workspace\u003C\u002Fa> made for that run alone. It is not shared with any other run or enterprise,\nand it is destroyed when the run finishes; a run waiting at a gate keeps its workspace until it carries on. Anything\nthe run did not push or publish goes with it.\u003C\u002Fp>\n\u003Ch2 id=\"what-the-model-sees\">What the model sees\u003C\u002Fh2>\n\u003Cp>The model a run uses is given the job: the task's goal, success metric, guardrails and skill, the run's input, and\nthe tools it may call, each as a name, a description and the arguments it takes. What a tool returns during the run\n(a file, an issue, an answer from memory) is read by the model too.\u003C\u002Fp>\n\u003Cp>A run also knows the date and time, with no tool to call. Its first message, ahead of its input, gives the moment\nthe run started to the minute, with the weekday, in UTC and in your enterprise's timezone. That timezone is named\nin the message and its offset from UTC is shown, daylight saving included. A skill can say &quot;due in the next four\nweeks&quot;, &quot;today&quot; or &quot;older than a week&quot; and rely on it, and &quot;today&quot; and &quot;here&quot; mean your enterprise's timezone. If the\nenterprise has no timezone the OS knows, the time is given in UTC only. A run that is retried, recovered or resumed\nis told the moment it resumed, not when the work first started. A run is told the time only when it starts or resumes,\nnot again at each step, and chat states it on every message. The time is never in the skill, so what a task sends\nthe model ahead of it stays the same from run to run.\u003C\u002Fp>\n\u003Cp>It is never given where a tool lives or how it signs in. Server addresses, tokens and other credentials stay with\nthe OS, which makes each call on the model's behalf, after the task's checks and any \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">gate\u003C\u002Fa>.\nAn argument a connection fixes (an organisation, a workspace) is taken out of what the model is shown, so it\ncannot ask for another.\u003C\u002Fp>\n\u003Cp>The model provider sees what a run sends it, on the \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend#model-connections\">model connection\u003C\u002Fa> you\nchose.\u003C\u002Fp>\n\u003Ch2 id=\"how-long-run-history-is-kept\">How long run history is kept\u003C\u002Fh2>\n\u003Cp>Executions and their runs are kept for your plan's period, counted from when the whole\n\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fexecutions\">execution\u003C\u002Fa> finished:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Plan\u003C\u002Fth>\n\u003Cth>Executions and runs kept for\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Free\u003C\u002Ftd>\n\u003Ctd>7 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Starter\u003C\u002Ftd>\n\u003Ctd>7 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Company\u003C\u002Ftd>\n\u003Ctd>30 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Scale\u003C\u002Ftd>\n\u003Ctd>30 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Enterprise\u003C\u002Ftd>\n\u003Ctd>365 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>After that, the execution is deleted whole: every run in it, with its logs, events and results. An execution is\nnever split, and one with a run still open is never deleted, however old its first run is. A clean-up runs every\nhour.\u003C\u002Fp>\n\u003Cp>Memory is kept until someone removes it. Removing a note hides it from every run at once; the record of it stays for\naudit.\u003C\u002Fp>\n\u003Ch2 id=\"mail-retention-by-plan\">Mail retention by plan\u003C\u002Fh2>\n\u003Cp>A member's mail is kept for your plan's period, then deleted: received mail and the member's own sent copies alike,\nwith their attachments, once they are older than it.\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Plan\u003C\u002Fth>\n\u003Cth>Mail kept for\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Free\u003C\u002Ftd>\n\u003Ctd>7 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Starter\u003C\u002Ftd>\n\u003Ctd>7 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Company\u003C\u002Ftd>\n\u003Ctd>30 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Scale\u003C\u002Ftd>\n\u003Ctd>30 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Enterprise\u003C\u002Ftd>\n\u003Ctd>365 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>The clean-up runs every hour, so mail goes within the hour of passing the period. Deleted mail is gone from the\ninbox, from the member's tasks and from file storage. A move to a plan that keeps mail for less time deletes what is\nolder than the new period at the next clean-up after the move; \u003Cstrong>Billing\u003C\u002Fstrong> says so before you change plan.\u003C\u002Fp>\n\u003Cp>Mail past the plan's daily inbound cap is held until the mailbox has room, and kept no longer than this period. The\ncap, and the other rules of a member's inbox, are on \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fmembers\">Members and inboxes\u003C\u002Fa> and\n\u003Ca href=\"\u002Fdocs\u002Femail\u002Fmember-mailboxes#inbound-mail-a-day\">Member mailboxes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"retention-you-set\">Retention you set\u003C\u002Fh2>\n\u003Cp>You will set how long your enterprise keeps run logs, memory and \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fassets\">assets\u003C\u002Fa>, within what your\nplan allows. Custom retention is part of the Enterprise plan.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"support-access\">Support access\u003C\u002Fh2>\n\u003Cp>Zero Human staff will not read your memory, logs, assets or secrets by default. When you need help, you will grant\nsupport access yourself: for a limited time, and recorded, so you can see who looked and when.\u003C\u002Fp>\n\u003C\u002Fdiv>\n\u003Ch2 id=\"closing-your-enterprise\">Closing your enterprise\u003C\u002Fh2>\n\u003Cp>Deleting an enterprise happens in two stages. It is closed at once, and its subscription is cancelled at once. Then,\nonce its plan's retention has passed, everything it holds is erased. The erasure cannot be undone.\u003C\u002Fp>\n\u003Ch3 id=\"who-can-delete-it\">Who can delete it\u003C\u002Fh3>\n\u003Cp>Only the enterprise's owner, signed in to the portal. At the end of \u003Cstrong>Enterprise\u003C\u002Fstrong>, the owner uses \u003Cstrong>Delete\nenterprise\u003C\u002Fstrong> in the \u003Cstrong>Danger zone\u003C\u002Fstrong> and confirms by typing the enterprise's name exactly: the same letters, in the\nsame case, with nothing before or after. A member who is not the owner is not offered it, and is refused if they ask.\nAn API token or a connected app cannot delete an enterprise. Who deleted it, and when, is recorded.\u003C\u002Fp>\n\u003Ch3 id=\"what-happens-at-once\">What happens at once\u003C\u002Fh3>\n\u003Cp>From the moment it is closed:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>The subscription is cancelled now.\u003C\u002Fstrong> A paid plan's subscription is cancelled at once, not at the end of the\nterm, with no refund or proration for the period already paid. Only this enterprise's subscription is cancelled,\neven when the same payer pays for others. If the cancel cannot be confirmed, nothing is closed: the enterprise stays\nopen, the owner is told, and can try again.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Nobody can use it.\u003C\u002Fstrong> A session open in it, an API token issued for it and a connected app are refused on their\nnext request. People can still sign in: someone who also belongs to another enterprise that is still open carries\non in that one, and someone with none left is offered to create one.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Nothing runs.\u003C\u002Fstrong> No run starts, whoever or whatever asks: a person, chat, the API, a webhook, a schedule or a\ntask that follows another. A run that was waiting in the queue is not picked up, and every run still in progress\nis cancelled, with its open \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">gates\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Mail is refused.\u003C\u002Fstrong> Mail to its addresses, on its own domain and on any domain it attached, is refused at the\ndoor, so it is never stored.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>What it published is deprecated.\u003C\u002Fstrong> Its tasks, roles and team templates in the catalog can no longer be cloned,\ncopied or synced. What another enterprise already cloned from them keeps working.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"the-retention\">The retention\u003C\u002Fh3>\n\u003Cp>A closed enterprise is kept for its plan's retention, counted from the moment it was closed, on the plan it held\nbefore the cancel:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Plan\u003C\u002Fth>\n\u003Cth>Kept for\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Free\u003C\u002Ftd>\n\u003Ctd>7 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Starter\u003C\u002Ftd>\n\u003Ctd>7 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Company\u003C\u002Ftd>\n\u003Ctd>30 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Scale\u003C\u002Ftd>\n\u003Ctd>30 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Enterprise\u003C\u002Ftd>\n\u003Ctd>365 days\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>An enterprise closed before deletion went by plan keeps the 30 days it was promised. During the retention:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Only Zero Human staff can reopen it, when its owner deleted it. Ask through support. Who reopened it, and when, is\nrecorded. One \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fisolation#closed-for-inactivity\">closed for inactivity\u003C\u002Fa> is different.\u003C\u002Fli>\n\u003Cli>Once it is reopened, runs and schedules work again. Schedules carry on from where they stood. Runs that closing\ncancelled stay cancelled, the subscription stays cancelled, and the catalog entries stay deprecated.\u003C\u002Fli>\n\u003Cli>Its slug stays taken, so no other enterprise can be created with it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3 id=\"what-is-erased-after-the-retention\">What is erased after the retention\u003C\u002Fh3>\n\u003Cp>Once the retention has passed, the enterprise is erased for good. The check runs every hour. Erased from every live\nstore:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>What\u003C\u002Fth>\n\u003Cth>Erased\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Runs and executions\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Every run and execution, with their inputs, logs, events, results and costs.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Memory\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The enterprise's memory bank, every note in it.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Mail\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Every member's inbox: the messages, their bodies and their attachments.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Files\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Everything kept in file storage for the enterprise: run logs, run files and mail bodies.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Secrets\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Model connections, tool connections, the webhook secret and API tokens.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Catalog\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>What it published that no other enterprise has cloned. An entry another enterprise still clones stays, deprecated, and goes once the last clone has gone.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Everything else\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Teams, roles, members, tasks, KPIs, the metered usage the usage reports were worked out from, attached domains, the people's access to the enterprise, and the enterprise itself.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>Another enterprise's data is never touched, even one the same people belong to. An erasure that is interrupted\nfinishes on the next check.\u003C\u002Fp>\n\u003Cp>What is kept:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>A minimal record of the close:\u003C\u002Fstrong> the enterprise's id, who closed it and when, when it was to be erased, who\nreopened it and when, and when it was erased. It holds no name, no slug and nothing the enterprise held.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The slug, retired for good.\u003C\u002Fstrong> It is never given to another enterprise, so mail and webhooks meant for this one\nnever reach a stranger.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The usage reports:\u003C\u002Fstrong> what was billed for each closed period, kept as the financial record. Your invoices stay\nwith our payment provider as its record.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>People's accounts and sessions.\u003C\u002Fstrong> A person outlives any one enterprise: a session that was in the erased\nenterprise stays signed in, to no enterprise.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Database backups are not edited: they expire on their own rolling schedule.\u003C\u002Fp>\n\u003Ch3 id=\"closed-for-inactivity\">Closed for inactivity\u003C\u002Fh3>\n\u003Cp>A Free enterprise nobody uses is closed for inactivity, after notice to its owners, and then erased. A paid plan\nnever closes for silence. The \u003Cstrong>Closes for silence\u003C\u002Fstrong> row on \u003Ca href=\"\u002Fpricing\">pricing\u003C\u002Fa> gives every plan's rule, and this\nsection is the one place in the docs that gives Free's numbers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What counts as activity.\u003C\u002Fstrong> Anything a person does in the enterprise: a signed-in person using it in the portal, a\ncall with one of its API tokens, or a connected app acting on a person's connection. What happens without a person\nnever counts: a scheduled run, a run the OS starts by itself, a built-in task, a clean-up, or anything Zero Human staff\ndo. Inbound mail never counts either, so an inbox that only receives mail does not keep an enterprise open. The\nsilence is counted from the last activity.\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The notices.\u003C\u002Fstrong> Free's schedule, as the plan row states it: notices at 30, 45 and 55 days of silence, closes at 60.\nEach notice is a mail to the enterprise's owners, and carries \u003Cstrong>Keep my enterprise\u003C\u002Fstrong>: one click keeps the enterprise\nopen, and counts as activity, so the silence starts again from there.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The close.\u003C\u002Fstrong> On the close day an enterprise nobody has used is closed, the way its owner's delete closes it (see\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fisolation#what-happens-at-once\">What happens at once\u003C\u002Fa>), and its owners are told.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The owner's reopen and the erase.\u003C\u002Fstrong> Until it is erased, an owner can reopen the enterprise in the portal, without\nasking support. It is erased 7 days after the close, Free's retention, as\n\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fisolation#what-is-erased-after-the-retention\">What is erased after the retention\u003C\u002Fa> sets out.\u003C\u002Fp>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,28,32,35,38,42,45,48,51],{"id":13,"text":14,"level":15,"planned":8},"one-enterprise-one-tenant","One enterprise, one tenant",2,{"id":17,"text":18,"level":15,"planned":8},"throwaway-run-environments","Throwaway run environments",{"id":20,"text":21,"level":15,"planned":8},"what-the-model-sees","What the model sees",{"id":23,"text":24,"level":15,"planned":8},"how-long-run-history-is-kept","How long run history is kept",{"id":26,"text":27,"level":15,"planned":8},"mail-retention-by-plan","Mail retention by plan",{"id":29,"text":30,"level":15,"planned":31},"retention-you-set","Retention you set",true,{"id":33,"text":34,"level":15,"planned":31},"support-access","Support access",{"id":36,"text":37,"level":15,"planned":8},"closing-your-enterprise","Closing your enterprise",{"id":39,"text":40,"level":41,"planned":8},"who-can-delete-it","Who can delete it",3,{"id":43,"text":44,"level":41,"planned":8},"what-happens-at-once","What happens at once",{"id":46,"text":47,"level":41,"planned":8},"the-retention","The retention",{"id":49,"text":50,"level":41,"planned":8},"what-is-erased-after-the-retention","What is erased after the retention",{"id":52,"text":53,"level":41,"planned":8},"closed-for-inactivity","Closed for inactivity",1794928142848]