# Set up a door

A door is where a company's employees, partners or customers come in. Setup chooses what it is for, how it looks, what people do first and who they ask, and nobody sees a change until you publish it.

Each company in Kapi Works has three doors: one for its employees, one for its partners and one for its customers. A door is what those people see when they sign in: its Home and pages, the steps they take first, the terms they accept, its forms and folders, and who to ask. Every door has the same sign-in and course player, in Kapi Works' own frame; Setup changes what is inside.

In Works Studio, open an audience, such as **Partners**, then **Setup**. On the left are Setup's controls, or Kapi, the setup helper; on the right is the door as people will see it, at a laptop's width or a phone's. Every change saves to the door's draft at a pause. People see the version you last published until you publish again.

On a door nobody has set up yet, Kapi opens first and asks what the door is for. You can [set it up with Kapi](https://docs.kapiworks.com/build/doors/kapi) by talking to it, or choose **Set it up myself** and use the controls below. Both work on the same draft, and **Ask Kapi** opens Kapi again at any time.

## What it is for

The first choice is what the door is for. Each choice switches on a few parts, and every part can be switched on or off by itself afterwards.

| Door      | Choices                                                                             |
| --------- | ----------------------------------------------------------------------------------- |
| Partners  | Resellers, Referral partners, Technology partners, Services partners, Just learning |
| Employees | Training and policies, New starters, Just learning                                  |
| Customers | Product academy, Client onboarding, Certification, Just learning                    |

A part brings what it needs. **Deal registration** adds a Deals page with a **Register a deal** form, where you approve or decline each deal and the partner sees your answer. A kit or guides part adds a folder on Home, which people see once it has a file or page in it. **About you** and **New starters** add first steps. A part that needs something only the company has waits for it in its row: **Partner agreement** waits for a published policy, and **Certified to sell** or **Get certified** for a course shared with the door.

## Theme, colour and name

Choose one of Kapi's three themes, make one with Kapi, or upload your own; [Looks](https://docs.kapiworks.com/build/looks) explains each. Below the themes are the door's name, its welcome line, the email address people write to with questions, its colour, and its photo when the theme shows one.

## Home and pages

Home and each page are stacks of blocks: the welcome, the steps, your learning, courses, text, links, forms, folders, updates, who to ask and designed blocks. A page can be for everyone or for chosen teams, firms and partner levels. [Pages](https://docs.kapiworks.com/build/pages) explains the blocks and designed blocks.

## Before they start

What people do before the rest of the door:

* **Terms.** A policy everyone accepts first, such as a partner agreement or an acceptable use policy. Choosing a published one shares it with everyone in the door. The agreement Kapi makes a draft of is the door's terms at once: publish it in **Policies**, then publish the door.
* **Steps.** Things people do first: fill in a form, finish a course, accept a policy, open a file, tick off something themselves, or wait for you to tick it. A step can be for chosen teams or levels. A course or policy a step asks for is shared with the people the step is for.
* **Closed until they finish.** The rest of the door can stay closed until the steps are done. Until then people see the steps, what each step opens, Account and Sign out.

## Forms

The door's forms, such as **Register a deal**, **About you** or **Kick-off questions**. A form takes one answer from each person, or one for each thing they send, such as each lead. A form can ask for your decision on each answer: you approve or decline it with a reason, and the person sees your answer. The people who decide get an email when an answer waits, then, each working morning in your time zone, one email listing the answers still waiting: after one, two and three working days, then on Mondays, until each is decided. From the third working day the owners and admins hear too when managers decide.

A question can ask for files: PDF, Word or pictures, up to 10 MB each, one file or up to 5 or 10, as you choose. People choose a file and it uploads at once; whoever can read the answer opens it from **Answers**. Files stay with their answer and are deleted with it. Answers stay for as long as the form says. When you change the questions after people have answered, each answer keeps the questions it answered.

## Partner levels

Partner doors can have levels, such as Registered, Silver and Gold. A partner firm holds a level for everyone at the firm, and someone in no firm holds one of their own. Pages, blocks and steps can be for chosen levels, and finishing the steps can move a firm up to a level.

## Who to ask

The address people write to with questions shows first, as **Questions**. After it come the people you name: someone on your Studio team, with their name, a role line and their email address, or a named address such as an IT help desk. They show in the door's **Who to ask** block, which goes on Home with the first of them, and on its terms and steps pages.

## Who can come in

You invite people from the audience's **People**, or from **Add people** in the menu. A partner door can let each partner firm have an admin, who invites colleagues on the firm's email domains. A customer door can also let people join with a join code or from approved email domains, into a client firm you choose.

## Preview and publish

**Laptop** and **Phone** show the draft beside Setup; **Preview** shows it across the window. **See it as** shows the door to someone in a chosen team, firm or level. When something would stop the door working, such as a step whose course isn't shared yet, Setup shows **Fix first** and outlines it where it is. **Publish** names what changed; people see it the next time they open a page. **History** keeps every version you published, to look at again or use as the draft.
