Set up web apps

Org admins deploy the organization's web app site once, on Netlify or your own infrastructure, then turn web apps on for members.

Members publish apps to a single site that belongs to your organization. An org admin sets it up once. The site is built from a GitHub repository your organization owns, and by default Keyboard deploys it to Netlify for you.

You can do the whole setup from your AI client, with the dashboard handling the steps that involve tokens. Ask:

"Set up web apps for our organization."

The agent checks where setup stands and tells you the next step every time. Follow it until the site is live.

What you need

A GitHub repository for the site, as owner/name.
The Netlify GitHub App installed on that repository, and its installation ID.
A site name: 3 to 63 lowercase letters, digits or hyphens.
A GitHub token and a Netlify token. You enter these on the dashboard, not in chat.

If your organization runs Keyboard in its own infrastructure, you host the site yourself.

A GitHub repository for the site, as owner/name.
The https address the site is served from.
Where you deploy it: Kubernetes, Netlify, Container Apps, or other.

Steps

Configure. Tell the agent the repository and site details. It saves them and gives you a dashboard link.
Add the tokens. Open the link and enter the tokens there.

Warning
Never paste tokens into the chat. Keyboard only accepts them on the dashboard. After a token is saved, the repository can only be changed on the dashboard too, so a token is only ever used on the repository you saw when you added it.
Deploy. Ask the agent to deploy. Creating and building the site takes a few minutes, and the agent checks on it until it's done.
Turn web apps on. Members can't use web apps until an admin turns them on in the Keyboard dashboard, on the Web apps page. Until then, members' agents tell them web apps aren't available.

Set a house style

Write a style note: colors, tone, layout, and anything apps should always or never include. The agent follows it whenever a member builds or edits an app.

"Set our web app style note: use our navy and white palette, keep layouts simple and mobile-friendly, and always show the signed-in user in the header."

You can change the style note at any time.

Keep the site up to date

The Web apps page in the dashboard shows when your site has fallen behind Keyboard's latest app shell. Nothing is pushed to your site automatically. When you're ready, ask the agent to redeploy, or update from the dashboard.

Tearing the site down is done on the dashboard only.

Auditing apps

The Web apps page lists every app in your organization. Each app has its own page showing:

who created it and who published it last;
the connections it declares;
who it's shared with;
its files, and the packages and versions it uses.

Every call an app makes through Keyboard is logged: the viewer, the connection, the method, the host, and the path, plus the upstream status. API usage is broken down by app, so you can see which apps are used and how heavily.

Apps reach company systems only through Keyboard and only through the connections they declare. To control what your organization's agents can reach more broadly, see Security policies.