How to get Fieldbook running at your company

Installing Fieldbook means creating your company’s own copy and connecting it to a few services. Your role is to decide who it is for and how you want to use it. IT or GTM Engineering can connect the services or give you the access to do it with an AI agent.

I've run multiple agent-assisted fresh installations and they complete in about 30 minutes, with a person helping with credentials, logins, and a few decisions. Getting company access or approval may take longer than the setup itself.

Four pieces work together. If your company already uses Vercel, Supabase, and Google, these may be familiar to the people helping you.

Once these are connected, you manage content, people, assignments, and organization settings through Fieldbook’s interface.

Start with a small request to the right people.

You can give IT or GTM Engineering this article and send a note like this:

I’d like to set up Fieldbook for our enablement team. It uses a company-owned copy of the source code, a Vercel project, a dedicated Supabase project, and Google sign-in.

Could you help create those projects and connect them, or give me the appropriate access to work through the setup with an AI agent?

We’ll also need someone who can create a Google OAuth Web application client and, if required by company policy, approve it for employee sign-in. It only needs basic identity information: name, email address, and profile.

Our first Fieldbook administrator will be [email address]. Our intended audience is [employees only / employees and approved external users]. Our preferred web address is [address, or use the Vercel address initially].

You can remain Fieldbook’s administrator while someone else owns the infrastructure accounts. They can enter credentials directly into the appropriate services.

Choose the exact Google email address of the person who will initially manage Fieldbook. This is your first administrator, and it must be established at setup.

You should also consider:

• Web address: Use the address Vercel provides, or ask for a company address such as https://learn.example.com. (opens in a new tab) A custom domain is optional.
• Audience: Decide whether this is for employees only or whether contractors, partners, or other approved people also need access. For an internal enablement site, plan to use members-only browsing and closed registration. You’ll apply those settings after the first administrator signs in.

Installing Fieldbook.

They copy the Fieldbook source (opens in a new tab) into your company’s GitHub account, then create a dedicated, empty Supabase project.

A Supabase project is a separate space for this installation’s data. Use a new project rather than adding Fieldbook to the database behind another company application.

The Supabase project supplies four useful pieces of information:

• Project reference: The project’s identifier, used by the database installer.
• Project URL: The address the application uses to reach Supabase.
• Publishable key: Identifies the application’s browser connection to Supabase.
• Secret key: Gives the application’s server privileged access to its data.

The project URL and publishable key are available through the project’s Connect dialog. Keys can also be found under Settings → API Keys. The secret key belongs in protected server configuration; use your company’s credential-sharing process if another person needs it. Supabase’s key guidance (opens in a new tab) explains the distinction.

Next, Vercel needs to know how to run Fieldbook. You, your AI agent, or your IT contact imports the company’s GitHub copy into a new Vercel project and selects the branch that will run the live application.

These are the application’s build settings:

These tell Vercel how to prepare and run the existing application.

The six Vercel connection settings are just six named values. Vercel calls them environment variables. Think of them as a setup form: where is the database, which credentials should the server use, what is the website’s address, and who should become the first administrator?

Open the Vercel project’s Environment Variables settings and add these to Production, the environment for the live installation.

The first three come from Supabase. The next two come from your decisions. The last one tells Vercel to build the installed application.

Copy complete keys, rather than shortened values shown in a dashboard. Keep the secret key under its exact name above; the NEXT_PUBLIC_ prefix is reserved for values the browser can receive.

Deploy the application after saving the settings. If the assigned Vercel address differs from FIELDBOOK_URL, correct that value and redeploy. Changes to environment variables take effect in a new deployment. Vercel’s instructions (opens in a new tab) show where to enter and update them.

The database setup is one guided command. Your helper or agent needs a local copy of the same source version and Node.js 22, the software that runs the installer.

From the main folder of that source copy, run:

node scripts/setup-database.mjs

The installer asks for the Supabase project reference and the deployed Fieldbook address. It shows the target, asks you to confirm by typing SETUP, and guides you through Supabase login.

It then creates Fieldbook’s database structure, private media storage, and scheduled deletion cleanup. Your helper can check the result using the technical installation guide.

If your company uses Vercel deployment protection, your helper should also check that scheduled cleanup can reach Fieldbook’s cleanup endpoint. Fieldbook’s own members-only setting allows that connection.

Google sign-in needs someone with Google Cloud access. Having a company Google account gives you a way to sign in; creating the sign-in connection requires permission in a Google Cloud project.

Start with IT or the person who manages Google Workspace—the team that handles company Google accounts. Ask them to route this request:

Who can create a Google OAuth Web application client in a company-owned Google Cloud project, and who approves new “Sign in with Google” applications for employees?

Those responsibilities may belong to different people. A Cloud administrator creates the connection. A Workspace administrator may need to approve its use under company policy.

OAuth is the name of the connection that lets Google confirm a user’s identity to Fieldbook. For this setup, it requests only basic identity information.

Give the Google Cloud administrator these specific instructions. In a company-owned Google Cloud project, open Google Auth Platform and configure:

• Branding: A recognizable application name and support contact.
• Audience: Internal for users within the project’s Google organization, where available. Use External if approved users outside that organization need to sign in.
• Data Access: Only openid, email (userinfo.email), and profile (userinfo.profile).
• Clients: Create an OAuth client with application type Web application.

Internal Google audience settings limit authorization to the organization. Fieldbook’s registration settings let you further control who joins the installation. Google’s audience guidance (opens in a new tab) explains these choices.

The Web application client needs two addresses:

Creating the client produces a client ID and client secret. Save the complete secret when it is created; Google may show only a shortened version afterward. Google’s client guidance (opens in a new tab) explains credential handling.

If company policy blocks new sign-in applications, give the client ID to the Google Workspace administrator so they can approve its basic sign-in permissions through the company’s app access controls (opens in a new tab).

Finish the Google connection in Supabase. Your Supabase helper opens Authentication → Sign In / Providers → Google, enables Google, and enters that client ID and client secret. Supabase’s Google setup guide (opens in a new tab) covers this connection.

Then, under Authentication → URL Configuration, set:

These addresses describe the return journey after sign-in:

Google confirms your identity → Supabase establishes your session → Fieldbook opens your account.

That is why Google’s callback points to Supabase, while Supabase’s callback points to Fieldbook. The addresses must match the actual projects and website you created. Supabase’s redirect guidance (opens in a new tab) explains how the allowed addresses work.

Sign in and choose who can enter.

Open Fieldbook and sign in using the exact address saved as FIELDBOOK_OWNER_EMAIL during setup. Its first verified registration creates the administrator account.

Choose this email before the person first registers. Changing the environment variable later does not transfer administrator access.

A new installation starts with public browsing and open registration. Before adding internal company content, open Manage organization → Access and set:

• Members-only browsing: People must sign in to read published content.
• Closed registration: Only people you have added in People can register.

Add each person using the Google email they will sign in with. Fieldbook does not send an invitation email, so share the website address with them yourself.

Check the experience before sharing it widely.

Confirm that you can sign in as the administrator, publish a small test Doc, and have a preregistered colleague sign in and read it. For a members-only installation, also check that a signed-out browser cannot read the content.

Your new installation starts empty. You can then set its name, prepare the home page, add your people, and begin building Updates, Courses, and Docs.

Ask AI and connections to external AI tools are optional additions. You can set those up once the core installation is working.

Keep the project links and a named technical contact for future updates. From there, your everyday work happens in Fieldbook: publishing useful content and helping your team learn.