Skip to lesson

Lesson 4 of 7 · HQ fundamentals

Deploy a Private HQ App

Build a small web app with HQ, make it visible only to your company, and check that outsiders can’t get in.

Begin lesson
Written path
6 steps

Before You Begin

  1. HQ is signed in to a company that’s set up for your team (see Lesson 2).

  2. You know roughly what you want the page to show.

  3. You know which company should own it and who should see it.

  4. You can open a private or incognito browser window to test it.

Step-by-step walkthrough

  1. Step 1: Describe the app

    Run /deploy and describe what you want. Stick to information that’s fine for your team to see, and don’t ask the page to show any API keys.

    CommandType exactly as shown
     /deploy
 Create a mini site that summarizes approved company information without exposing credentials.
    Expected

    HQ starts building the app.

  2. Step 2: Pick the company, if HQ asks

    HQ usually knows the company from the folder you’re in. If you’re in more than one company, it shows you a preview and asks which one should own the app before it publishes anything.

    PromptSend in your AI session
     Deploy this to [company name].
    Expected

    The app belongs to the right company.

  3. Step 3: Make it company-only

    Tell HQ that only your company should be able to see it.

    PromptSend in your AI session
     Please make it company-only, so only members signed in to [company name] can see it.
    Expected

    HQ locks the app so people have to sign in as a member of your company.

  4. Step 4: Wait for it to go live

    Keep the session open while HQ builds the app, shows you a preview, runs its safety checks, and publishes it.

    Expected

    HQ tells you the app is live, only your company can see it, and it tested the sign-in page.

  5. Step 5: Open it while signed in

    Open the link HQ gives you in your usual browser, where you’re signed in.

    Go toOpen this place
     Open the app link in your usual browser
    Expected

    The app loads, and no API keys are visible.

  6. Step 6: Make sure outsiders can’t get in

    Open a private browser window and go to the same link without signing in.

    Go toOpen this place
     Open the app link in a private browser window
    Expected

    You get a sign-in page instead of the app.

You’re done when

Your teammates can open the app after signing in, a private window gets a sign-in page, and no API keys show up on the page.

Hit a snag? Here’s the fix.

HQ deployed to the wrong company

Say “deploy this to [company name]” and run it again. Re-deploying the same project updates the same link.

The page opens without asking anyone to sign in

Ask HQ to redeploy it company-only. Every link has exactly one access level, and public is the default.

A teammate sees a sign-in wall they can’t get past

They need to sign in with the email that’s a member of your company. If they aren’t a member yet, invite them first.

Something else going on? The HQ knowledge base walks through the most common fixes, or reach out and we’ll help you get unstuck.