[{"data":1,"prerenderedAt":467},["ShallowReactive",2],{"docs-navigation":3,"docs-\u002Fworkspace\u002Fpeople-and-roles":254,"surround-\u002Fworkspace\u002Fpeople-and-roles":464},[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":183,"body":256,"description":186,"extension":457,"hidden":458,"meta":459,"navTitle":460,"navigation":461,"path":184,"seo":462,"stem":185,"__hash__":463},"docs\u002F5.workspace\u002F1.people-and-roles.md",{"type":257,"value":258,"toc":446},"minimark",[259,268,318,323,328,333,338,342,345,352,355,359,366,373,376,394,398,401,405,408,412,443],[260,261,262,263,267],"p",{},"Three roles. Each person in the workspace has one — ",[264,265,266],"strong",{},"in this workspace",".\nSomebody in more than one holds a role in each, and they do not have to match.",[269,270,271,284],"table",{},[272,273,274],"thead",{},[275,276,277,281],"tr",{},[278,279,280],"th",{},"Role",[278,282,283],{},"Can",[285,286,287,298,308],"tbody",{},[275,288,289,295],{},[290,291,292],"td",{},[264,293,294],{},"Owner",[290,296,297],{},"Everything below, plus managing the team, renaming the workspace, setting its domain, deleting applications, clearing out an application's data, and downloading the source",[275,299,300,305],{},[290,301,302],{},[264,303,304],{},"Builder",[290,306,307],{},"Create applications, direct the builder, save versions, deploy, publish files, add and correct records",[275,309,310,315],{},[290,311,312],{},[264,313,314],{},"Viewer",[290,316,317],{},"Read applications, previews and what they have stored. Nothing that changes or ships anything",[319,320,322],"h2",{"id":321},"choosing-one","Choosing one",[260,324,325,327],{},[264,326,314],{}," for somebody who needs to see what is being built — a stakeholder, a\ncolleague in another department, a client if you have given them an account.",[260,329,330,332],{},[264,331,304],{}," for anybody doing the work. This is most people.",[260,334,335,337],{},[264,336,294],{}," for the small number of people who should be able to delete things,\nchange the workspace domain, and take the source away.",[319,339,341],{"id":340},"the-roles-apply-to-the-builder-too","The roles apply to the builder too",[260,343,344],{},"This is the part worth understanding.",[260,346,347,348,351],{},"When you ask the builder to do something — deploy, add a user, connect a\ndomain — it acts ",[264,349,350],{},"as you",". Your role is resolved and enforced in exactly the\nsame code the buttons go through.",[260,353,354],{},"So a viewer cannot deploy by asking nicely, and an owner-only action stays\nowner-only however it is phrased. There is no way round the roles through the\nconversation, which is the point.",[319,356,358],{"id":357},"adding-somebody","Adding somebody",[260,360,361,362,365],{},"An owner presses ",[264,363,364],{},"Add teammate"," on the Team page and gives an email address\nand a role.",[260,367,368,369,372],{},"If that address is ",[264,370,371],{},"new to the platform",", set a password for them to start\nwith and pass it on. If it already has an account — because they work in\nanother workspace, perhaps yours and a client's — they simply join this one and\nkeep the password they already had.",[260,374,375],{},"Roles can be changed afterwards from the dropdown beside each person, and\nsomebody can be taken out with the button at the end of their row. Removing\nthem signs them out of this workspace at once and touches nothing else they\nhave: their account, and any other workspace they are in, carry on.",[377,378,379],"note",{},[260,380,381,382,385,386,389,390,393],{},"These are ",[264,383,384],{},"platform"," accounts — people who use the workbench. The people who\nsign in to an application you built are a separate thing entirely, kept under\n",[264,387,388],{},"Users",". See ",[391,392,134],"a",{"href":135},".",[319,395,397],{"id":396},"the-last-owner","The last owner",[260,399,400],{},"A workspace with no owner cannot be administered by anybody, and there is no\nway back from that. So the only owner cannot be stepped down, removed, or leave\nof their own accord. Make somebody else an owner first, and then any of the\nthree is fine.",[319,402,404],{"id":403},"sessions","Sessions",[260,406,407],{},"Signing in creates a session that can be revoked immediately. Removing somebody\nfrom the workspace, or suspending them, signs them out at once rather than\nwaiting for something to expire.",[319,409,411],{"id":410},"what-only-an-owner-can-do","What only an owner can do",[413,414,415,419,422,425,432,438],"ul",{},[416,417,418],"li",{},"Manage the team.",[416,420,421],{},"Rename the workspace and set its domain.",[416,423,424],{},"Delete an application.",[416,426,427,428,431],{},"Empty or delete a table, or empty a whole environment, on the\n",[391,429,430],{"href":165},"Data"," tab.",[416,433,434,435,393],{},"Remove somebody from the ",[391,436,437],{"href":135},"user directory",[416,439,440],{},[264,441,442],{},"Download source.",[260,444,445],{},"That last one is deliberate: taking an application away in full is a considered\nact with a technical colleague in mind, not something to do by accident.",{"title":447,"searchDepth":448,"depth":448,"links":449},"",3,[450,452,453,454,455,456],{"id":321,"depth":451,"text":322},2,{"id":340,"depth":451,"text":341},{"id":357,"depth":451,"text":358},{"id":396,"depth":451,"text":397},{"id":403,"depth":451,"text":404},{"id":410,"depth":451,"text":411},"md",false,{},null,true,{"title":183,"description":186},"KRKthwYyKHItZ1jLEb1-aaLuByDww12PFmtjridfsQ8",[465,466],{"title":179,"path":175,"stem":180,"description":181,"children":-1},{"title":188,"path":189,"stem":190,"description":191,"children":-1},1790202296896]