Chapter 4
Boarding
Request access, wait for approval, sign in, understand the 7-day trial, and read the first screen.
The route
- 1Request accesscockpitai.io/request-access
- 2Wait for approvalan email: You are in
- 3Enter Cockpitsign in with Google
- 4Agree to the AI listbefore your first chat
- 5Consolechip says Sandbox
Cockpit is in private beta. Nobody can use it until their email address has been approved, and approval is for the exact address you give. Use the test Gmail from chapter 3 throughout.
4.1 Request access
Open cockpitai.io/request-access. The front page at cockpitai.io also has a Request access link under the Enter Cockpit button.
You should see A page titled Request access with four boxes.
In Email you sign in with, type the test Gmail address. If you are already signed in, the box is filled in and locked to your signed-in address, with the line "You are signed in as ... We approve this exact address."
Fill in Your name, Company and What would you use Cockpit for? In the last box, say plainly that you are doing a test drive with throwaway accounts for an architect-led team. Nothing else is required.
Click Request access.
You should see The page changes to: "Thank you. We have your request and will email you when you are in. Your 7-day Pro trial starts when you first sign in, no card needed."
CAUTION
If the page says "Enter a valid email address.", the address is mistyped. If it says "Could not send that. Please try again in a moment.", wait a minute and send again; nothing was recorded.
4.2 Wait for approval
On the Cockpit side, an administrator reads the request in an Admin page that only administrators see, and approves or declines the exact email address. Approving sends you an email with the subject You are in: welcome to Cockpit. It says to sign in with Google, and that your 7-day Pro trial starts when you first sign in.
If you sign in before you are approved, Cockpit does not let you in. It shows a waiting screen:
- A pill reading Waiting for approval.
- The sentence "Cockpit is in private beta, so request access and we will email you as soon as you are in."
- "You are signed in as ..." with your address.
- Three steps: ask for access with the button; requests are reviewed and you are emailed, usually within a day or two; once approved, reopen Cockpit and sign in with the same Google account.
- A Request access button, and the support address support@cockpitai.io.
CAUTION · Hidden Apple email
If you sign in with Apple and choose to hide your email, Apple gives Cockpit a relay address that can never match an approved address. The waiting screen then says so. Sign in with the email you were approved under, or add that email to your account and make it your primary one. For the test drive, use Google.
ADVISORY
The waiting screen also offers Delete account, so you can leave without a trace at any point, approved or not.
4.3 Sign in
When the approval email arrives, open cockpitai.io and click Enter Cockpit.
You should see A sign-in page with the Cockpit mark and one or two buttons: Google, and Apple where it is switched on. There is no email or password box.
Choose Google and sign in with the test Gmail you were approved under.
You should see After a moment the words "Opening Cockpit..." appear, then the console.
If this is your first sign-in, a dialog titled Before your first chat appears when you send your first message. See the next section.
ADVISORY · The desktop apps
In the Mac and Windows apps, Enter Cockpit opens your browser to sign in with Google, then hands you back to the app. On the Mac, the first time you open the app, macOS asks whether to open an app downloaded from the internet: click Open. Chapter 5 covers downloading the apps.
ARRIVING · Sign in to a team
Only for teams, switched on per customer. On a build with Teams switched on, a quiet line under the Google button reads Sign in to a team. It opens a door with an email and password form for people a Captain invited. If your sign-in page has no such line, ignore this: you sign in with Google as above. See chapter 9.
4.4 Your 7-day trial
The trial starts the first time you sign in, not when you request access or when you are approved. No card is asked for. A bar at the top of the console counts it down.
- During the trial: "Pro trial: N days left. No card needed."
- After it: "Your 7-day Pro trial has ended. You can still read everything." Cockpit becomes read-only: you can read everything, but you cannot start chats, decide approvals or change connections. The bar offers Join the waitlist for paid; online payment is not available.
- An administrator can extend or end a trial.
ADVISORY
Plan the test drive to fit inside the seven days. The MuleSoft trials are time-limited too, so make the accounts in chapter 3 shortly before you start.
4.5 Agreeing to the AI provider
Before your first chat, Cockpit asks you once to agree to your messages, and the results of the tools the Copilot uses for you, being sent to its AI provider. The dialog is titled Before your first chat. It names the provider, Anthropic (Claude), and what it does with the data: it answers every chat message and writes the code and configuration your chats ask for.
- Agree records your agreement and sends the message you were writing.
- Not now closes the dialog. Chat stays off; the message box shows "Chat is off until you agree to Cockpit sending your messages to its AI providers." with a Review and agree link.
- You can withdraw at any time under AI processing on the Account page. Chat stops until you agree again, and your chats stay.
ADVISORY
Chapter 2 explains where the data goes. The provider list has a version: if it changes, Cockpit asks you again.
4.6 Your first screen
After you sign in the console opens on the chat. This is what is on it. Chapter 5 describes every control in turn.
| Where | What | What to check on your first visit |
|---|---|---|
| Far left (bottom bar on a phone) | The rail: Console, Search chats, Approvals, Connectors, Account, and your profile menu. | Five icons, with an extra Admin icon only for administrators. |
| Top bar, left | Chats button, and a chip showing the connected org, or "No org connected". | "No org connected" is right: you have not connected anything yet. |
| Top bar, right | A Download for Mac or Download for Windows button, the mode chip, and the Brain button. | The mode chip says Sandbox. |
| Above the message box | A picker for the Salesforce org or MuleSoft connection this chat will use. | "No Salesforce org connected. Connect one." |
| Bottom | The message box: "Describe the outcome you want...", a microphone, and a send button. | The line beneath it: "Every write the Copilot proposes waits for your approval. Nothing ships without you." |
WARNING · Check the chip before anything else
The mode chip must say Sandbox ("Sandbox: read-only, nothing can be changed"). New accounts start in Sandbox, so it should. If it says Production, stop and open the chip to switch back, before you connect anything.
Boarding checklist
Boarding checklist
- Access requested with the test Gmail address.
- The approval email arrived (subject: You are in: welcome to Cockpit).
- Signed in with Google, with the same address.
- The 7-day trial bar shows days left, and no card was asked for.
- I agreed to the AI provider list (or I know where to do it).
- The mode chip says Sandbox.
- The Connectors page opens with a Salesforce card and a MuleSoft card at the top and the Connected and Available tabs below. Nothing of yours is connected yet.