[{"data":1,"prerenderedAt":431},["ShallowReactive",2],{"docs-navigation":3,"docs-\u002Fworkspace\u002Fmore-than-one-workspace":254,"surround-\u002Fworkspace\u002Fmore-than-one-workspace":428},[4,33,86,114,173,212,231],{"title":5,"path":6,"stem":7,"children":8},"Start","\u002Fstart","1.start",[9,13,18,23,28],{"title":10,"path":6,"stem":11,"description":12},"Start here","1.start\u002Findex","What Desifex is, and how to get an application of your own running.",{"title":14,"path":15,"stem":16,"description":17},"What Desifex is","\u002Fstart\u002Fwhat-desifex-is","1.start\u002F1.what-desifex-is","An application factory where conversation is the interface — and the handful of things it deliberately will not do.",{"title":19,"path":20,"stem":21,"description":22},"Your first application","\u002Fstart\u002Fyour-first-application","1.start\u002F2.your-first-application","From a sentence to something running, in about twenty minutes, with nothing to install.",{"title":24,"path":25,"stem":26,"description":27},"The workbench","\u002Fstart\u002Fthe-workbench","1.start\u002F3.the-workbench","A tour of the screen you will spend your time on — the conversation, the six tabs, and the menu.",{"title":29,"path":30,"stem":31,"description":32},"What to expect","\u002Fstart\u002Fwhat-to-expect","1.start\u002F4.what-to-expect","How long things take, what a good working rhythm looks like, and the parts that genuinely go wrong.",{"title":34,"path":35,"stem":36,"children":37},"Building","\u002Fbuilding","2.building",[38,41,46,51,56,61,66,71,76,81],{"title":34,"path":35,"stem":39,"description":40},"2.building\u002Findex","Getting what you actually wanted out of the conversation.",{"title":42,"path":43,"stem":44,"description":45},"Describing what you need","\u002Fbuilding\u002Fdescribing-what-you-need","2.building\u002F1.describing-what-you-need","How to phrase a request so that what comes back is what you meant.",{"title":47,"path":48,"stem":49,"description":50},"Watching a build","\u002Fbuilding\u002Fwatching-a-build","2.building\u002F2.watching-a-build","What the steps mean, what is happening underneath, and why you are not shown a log.",{"title":52,"path":53,"stem":54,"description":55},"Changing your mind","\u002Fbuilding\u002Fchanging-your-mind","2.building\u002F3.changing-your-mind","Interrupting a build, correcting a misunderstanding, and undoing something you asked for.",{"title":57,"path":58,"stem":59,"description":60},"When a build fails","\u002Fbuilding\u002Fwhen-a-build-fails","2.building\u002F4.when-a-build-fails","What a failure actually means, what to try, and when to ask us.",{"title":62,"path":63,"stem":64,"description":65},"Showing it a file","\u002Fbuilding\u002Fshowing-it-files","2.building\u002F5.showing-it-files","Attaching a screenshot, a spreadsheet or a document to the conversation — often faster than describing it.",{"title":67,"path":68,"stem":69,"description":70},"Choosing a design system","\u002Fbuilding\u002Fchoosing-a-design-system","2.building\u002F6.choosing-a-design-system","What a design system decides, how to pick one, and what changing it later does.",{"title":72,"path":73,"stem":74,"description":75},"Asking for settings","\u002Fbuilding\u002Fasking-for-settings","2.building\u002F7.asking-for-settings","The conversation reaches the whole platform — addresses, icons, redirects, users, integrations and shipping. If you do not know where a setting is, ask.",{"title":77,"path":78,"stem":79,"description":80},"When it asks you","\u002Fbuilding\u002Fwhen-it-asks-you","2.building\u002F8.when-it-asks-you","Some decisions arrive as a screen rather than a message — a table to correct, a list to choose from — and the build waits for your answer.",{"title":82,"path":83,"stem":84,"description":85},"Starting from what you have","\u002Fbuilding\u002Fstarting-from-what-you-have","2.building\u002F9.starting-from-what-you-have","A spreadsheet, a document, a picture or a page of your own site — attached, read, and built from.",{"title":87,"path":88,"stem":89,"children":90},"Shipping","\u002Fshipping","3.shipping",[91,94,99,104,109],{"title":87,"path":88,"stem":92,"description":93},"3.shipping\u002Findex","Getting what you built in front of people, and getting back to an earlier version.",{"title":95,"path":96,"stem":97,"description":98},"Versions","\u002Fshipping\u002Fversions","3.shipping\u002F1.versions","Every build is kept, named after what was asked for, and can be compared and restored.",{"title":100,"path":101,"stem":102,"description":103},"Environments","\u002Fshipping\u002Fenvironments","3.shipping\u002F2.environments","Preview, test and live — what each one is, who can reach it, and why their data is separate.",{"title":105,"path":106,"stem":107,"description":108},"Deploying","\u002Fshipping\u002Fdeploying","3.shipping\u002F3.deploying","Putting a version into test or live, what happens while it deploys, and what happens if it fails.",{"title":110,"path":111,"stem":112,"description":113},"Going back","\u002Fshipping\u002Fgoing-back","3.shipping\u002F4.going-back","Restoring an earlier version when a change turned out to be wrong.",{"title":115,"path":116,"stem":117,"children":118},"Running","\u002Frunning","4.running",[119,123,128,133,138,143,148,153,158,163,168],{"title":120,"path":116,"stem":121,"description":122},"Running it","4.running\u002Findex","Everything in Settings — addresses, access, people, files, integrations and what crawlers are told.",{"title":124,"path":125,"stem":126,"description":127},"Addresses and domains","\u002Frunning\u002Faddresses-and-domains","4.running\u002F01.addresses-and-domains","The address an application gets, and how to put it on a domain you own.",{"title":129,"path":130,"stem":131,"description":132},"Who can reach it","\u002Frunning\u002Fwho-can-reach-it","4.running\u002F02.who-can-reach-it","Open, behind one shared password, or accounts — and why the choice is enforced in front of the application.",{"title":134,"path":135,"stem":136,"description":137},"People who sign in","\u002Frunning\u002Fpeople-who-sign-in","4.running\u002F03.people-who-sign-in","The workspace's user directory — adding the people who use your applications, which ones each may open, what you can keep about them, and two-step sign-in.",{"title":139,"path":140,"stem":141,"description":142},"Published files","\u002Frunning\u002Fpublished-files","4.running\u002F04.published-files","Documents your application hands to its users — a price list, a brochure, a form — with a stable address and no build to change them.",{"title":144,"path":145,"stem":146,"description":147},"Integrations","\u002Frunning\u002Fintegrations","4.running\u002F05.integrations","Email, SMS and Google — connected once, used by the application without it ever holding a credential.",{"title":149,"path":150,"stem":151,"description":152},"Appearance","\u002Frunning\u002Fappearance","4.running\u002F06.appearance","The browser tab, the icon, what a link looks like when somebody pastes it, and adding it to a phone's home screen.",{"title":154,"path":155,"stem":156,"description":157},"Redirects and search engines","\u002Frunning\u002Fredirects-and-search-engines","4.running\u002F07.redirects-and-search-engines","Old addresses that still get visited, and what crawlers are told about each environment.",{"title":159,"path":160,"stem":161,"description":162},"Configuration values","\u002Frunning\u002Fconfiguration-values","4.running\u002F08.configuration-values","Named values the application needs but must not contain — API keys, account numbers, thresholds.",{"title":164,"path":165,"stem":166,"description":167},"Your data","\u002Frunning\u002Fyour-data","4.running\u002F09.your-data","The Data tab — reading, correcting, adding to and clearing out what your application has stored, one environment at a time.",{"title":169,"path":170,"stem":171,"description":172},"Visitors","\u002Frunning\u002Fvisitors","4.running\u002F10.visitors","Who is using the application, counted without identifying anybody and with nothing to set up.",{"title":174,"path":175,"stem":176,"children":177},"Workspace","\u002Fworkspace","5.workspace",[178,182,187,192,197,202,207],{"title":179,"path":175,"stem":180,"description":181},"Your workspace","5.workspace\u002Findex","What every application in it shares — the domain, the design systems, the people, the user directory and, if you want it, one set of records — and how to be in more than one.",{"title":183,"path":184,"stem":185,"description":186},"People and roles","\u002Fworkspace\u002Fpeople-and-roles","5.workspace\u002F1.people-and-roles","Three roles, what each can do, how they apply to the builder as well as to the buttons, and why they belong to a workspace rather than to an account.",{"title":188,"path":189,"stem":190,"description":191},"More than one workspace","\u002Fworkspace\u002Fmore-than-one-workspace","5.workspace\u002F2.more-than-one-workspace","Belonging to several, switching between them, the role you hold in each, and why nothing crosses over.",{"title":193,"path":194,"stem":195,"description":196},"Organising applications","\u002Fworkspace\u002Ffolders-and-organising","5.workspace\u002F3.folders-and-organising","Folders on the dashboard, and how to keep a growing list navigable.",{"title":198,"path":199,"stem":200,"description":201},"Your own design systems","\u002Fworkspace\u002Fyour-own-design-systems","5.workspace\u002F4.your-own-design-systems","Authoring a design system for your brand, or a client's, by importing guidelines, a website or a Figma library.",{"title":203,"path":204,"stem":205,"description":206},"Your profile","\u002Fworkspace\u002Fyour-profile","5.workspace\u002F5.your-profile","Your name, your password, your picture, and the theme.",{"title":208,"path":209,"stem":210,"description":211},"Where records live","\u002Fworkspace\u002Fwhere-records-live","5.workspace\u002F6.where-records-live","One store per environment, one across an application's environments, or one the whole workspace shares — what each costs you, and how to change it.",{"title":213,"path":214,"stem":215,"children":216},"Developers","\u002Fdevelopers","6.developers",[217,221,226],{"title":218,"path":214,"stem":219,"description":220},"For developers","6.developers\u002Findex","What is actually generated, and what to do when you inherit one.",{"title":222,"path":223,"stem":224,"description":225},"What gets built","\u002Fdevelopers\u002Fwhat-gets-built","6.developers\u002F1.what-gets-built","The stack, the shape of the repository, and the parts the platform provides rather than the application.",{"title":227,"path":228,"stem":229,"description":230},"Taking one over","\u002Fdevelopers\u002Ftaking-it-over","6.developers\u002F2.taking-it-over","For the developer who has just been handed an application built here.",{"title":232,"path":233,"stem":234,"children":235},"Reference","\u002Freference","7.reference",[236,239,244,249],{"title":232,"path":233,"stem":237,"description":238},"7.reference\u002Findex","Terms, limits, and what to do when something specific has gone wrong.",{"title":240,"path":241,"stem":242,"description":243},"Glossary","\u002Freference\u002Fglossary","7.reference\u002F1.glossary","Every term this documentation uses, in one place.",{"title":245,"path":246,"stem":247,"description":248},"Limits","\u002Freference\u002Flimits","7.reference\u002F2.limits","The boundaries that are real, so you do not discover them at an inconvenient moment.",{"title":250,"path":251,"stem":252,"description":253},"Troubleshooting","\u002Freference\u002Ftroubleshooting","7.reference\u002F3.troubleshooting","Specific symptoms, and what each one usually means.",{"id":255,"title":188,"body":256,"description":191,"extension":421,"hidden":422,"meta":423,"navTitle":424,"navigation":425,"path":189,"seo":426,"stem":190,"__hash__":427},"docs\u002F5.workspace\u002F2.more-than-one-workspace.md",{"type":257,"value":258,"toc":409},"minimark",[259,263,271,276,288,291,297,301,311,314,328,332,339,346,350,353,357,363,366,384,388,391,395,403],[260,261,262],"p",{},"One account, as many workspaces as you need. An agency has one per client. A\nconsultant has their own and the customer's. Somebody keeps an experiment\napart from the business it might one day be part of.",[260,264,265,266,270],{},"Each workspace keeps its own applications, its own people, its own design\nsystems, its own domain and its own user directory. ",[267,268,269],"strong",{},"Nothing crosses between\nthem"," — that is the whole reason to have a second one.",[272,273,275],"h2",{"id":274},"where-the-switcher-is","Where the switcher is",[260,277,278,279,283,284,287],{},"Top right, behind your picture. Every ",[280,281,282],"em",{},"other"," workspace you belong to is listed\nas ",[267,285,286],{},"Switch to"," it, and choosing one moves you there. When you are in more than\none, the name of the one you are in sits beside the menu, so which is which is\nnever a guess.",[260,289,290],{},"The whole screen reloads when you switch. That is deliberate: a dashboard still\nlisting the workspace you have left is how somebody deploys the wrong thing.",[292,293,294],"note",{},[260,295,296],{},"Switching ends the session you were in and starts a new one. You will not have\ntwo workspaces open in two tabs, which is the point — one client's work should\nnot be one mis-click away from another's.",[272,298,300],{"id":299},"starting-one","Starting one",[260,302,303,306,307,310],{},[267,304,305],{},"New workspace…"," in the same menu, or ",[267,308,309],{},"New workspace"," on the Team page.\nGive it a name and you are moved into it as its owner.",[260,312,313],{},"It starts empty. Applications, people and design systems belong to a workspace,\nand nothing is copied across — if you wanted them together they would not need\nto be two.",[292,315,317],{"type":316},"tip",[260,318,319,320,323,324,327],{},"Name it after the client or the business rather than after what is in it. It is\nthe name on every screen and in the switcher, and ",[280,321,322],{},"Acme"," reads better than\n",[280,325,326],{},"Acme CRM and portal"," once there are three applications in it.",[272,329,331],{"id":330},"the-role-you-hold-is-per-workspace","The role you hold is per workspace",[260,333,334,335,338],{},"You can be the owner of your own and a viewer in a client's. The role that\ndecides what you may do is the one you hold ",[267,336,337],{},"here",", not one attached to your\naccount.",[260,340,341,342,345],{},"So the same person, in two places on the same afternoon, can delete an\napplication in one and be unable to deploy in the other. See\n",[343,344,183],"a",{"href":184},".",[272,347,349],{"id":348},"joining-somebody-elses","Joining somebody else's",[260,351,352],{},"An owner there adds you by your email address. Because you already have an\naccount, you keep the password you already had — you are added rather than\nsigned up again, and the next time you sign in the workspace is in your\nswitcher.",[272,354,356],{"id":355},"leaving-one","Leaving one",[260,358,359,362],{},[267,360,361],{},"Leave"," next to it on the Team page. Your account and every other workspace\nare untouched.",[260,364,365],{},"Two things will stop you, both for the same reason — a door nobody can open:",[367,368,369,377],"ul",{},[370,371,372,373,376],"li",{},"You cannot leave your ",[267,374,375],{},"only"," workspace.",[370,378,379,380,383],{},"The ",[267,381,382],{},"last owner"," of a workspace cannot leave it. Make somebody else an\nowner first.",[272,385,387],{"id":386},"being-removed-from-one","Being removed from one",[260,389,390],{},"An owner can take you out of theirs. You are signed out of that workspace\nimmediately, and only that one: your own and any others carry on as they were.",[272,392,394],{"id":393},"what-this-does-not-change","What this does not change",[260,396,397,400,401,345],{},[267,398,399],{},"Applications, people and data stay where they are."," There is no moving an\napplication between workspaces, and no shared login between them. A person who\nsigns in to applications in two of your workspaces holds an account in each —\nsee ",[343,402,134],{"href":135},[260,404,405,408],{},[267,406,407],{},"Spend is still reported per workspace",", which is what makes a client a clean\nline in a bill.",{"title":410,"searchDepth":411,"depth":411,"links":412},"",3,[413,415,416,417,418,419,420],{"id":274,"depth":414,"text":275},2,{"id":299,"depth":414,"text":300},{"id":330,"depth":414,"text":331},{"id":348,"depth":414,"text":349},{"id":355,"depth":414,"text":356},{"id":386,"depth":414,"text":387},{"id":393,"depth":414,"text":394},"md",false,{},null,true,{"title":188,"description":191},"dXb8EM87og9EO3XpuBNy1FAnDnSq8iPFiSO3oaC57HM",[429,430],{"title":183,"path":184,"stem":185,"description":186,"children":-1},{"title":193,"path":194,"stem":195,"description":196,"children":-1},1790202296896]