Skip to content
GatlasHelp center

Onboarding guide

Everything a portfolio group needs to go from a new account to its first answer in Claude. Each step says who does it, and none of it needs anyone from Gatlas.

Who does what

Onboarding a portfolio touches a few people, and each of them only does their own part.

  • You, the person setting up Gatlas for the group. You create the account, build the company tree, decide who sees what, and check the numbers. You are the owner of the organization.
  • A contact at each company, usually the person in finance or operations who can sign in to that company's tools. They open a setup link you send, connect their tools, and are done. They never need a Gatlas account.
  • The people who ask questions: partners, finance leads or the companies' own teams. They get a Gatlas login, an MCP connection, or both, scoped to the companies they should see. An MCP connection is how AI assistants such as Claude connect to Gatlas.

Gather what you need first

An hour spent here saves a week of back and forth later. Before you sign up, write down:

  • Your companies, and how they group. A fund with a few holdings, a studio with ventures under it, or a flat list all work.
  • The tools each company keeps its numbers in: accounting, commerce, payments, CRM, analytics. Check them against the connectors; if one is missing, tell us.
  • One contact per company who can sign in to those tools, with a name and an email address.
  • The first questions you want answered. "Revenue by company by month" or "receivables older than 60 days" is a better start than "everything".
  • Who should see which companies once the data is in.

Create the account and the organization

1

Sign up

Go to gatlas.ai/signup and fill in Full name, Email, Password (at least 8 characters) and Organization name: the name of your holding company or fund. Create account signs you in and opens Entities.

If a colleague invited you instead, open the invitation email and choose Create account and join. Invitations expire after 7 days.

Build the company tree

2

Add your companies

On Entities, choose Add entity for each company. Every entity has a type:

  • Organization: the top-level umbrella everything hangs off.
  • Group: holds a set of companies beneath it.
  • Company: a company or business unit, where data actually syncs.

Set Parent entity to nest a company under a group. If your group calls these tiers something else, rename them under Settings, Entity labels.

3

Tell agents what each company is

Open a company and fill in Agent instructions under AI agent context: what the company does, its fiscal year, its currency, and anything a newcomer would get wrong. AI assistants read this when they start working with your data, so a few good sentences here pay off on every answer.

Connect each company's tools

Every company's tools connect to that company in Gatlas. You can connect them yourself, or send a setup link to the person who can. Most groups do both.

4

Connect a tool yourself

On Sources, choose Add source, pick the company and the tool, then either Connect with the tool (you sign in to it and approve access) or paste an API key. Each connector's requirements are on Connecting sources.

5

Or send a setup link

On Sources, open Setup links and choose Generate setup link, or use Setup link on the company's own page. Choose They choose to let the contact pick their tools, or You choose to name them. The link expires in 7 days unless you pick 30, and it can be emailed straight to the contact.

The contact opens the link without an account and presses Connect for each tool. If they chose the tools, they finish with That's everything; if you named them, the link completes once each one is connected. It takes most people a few minutes. Follow progress in the Status column of the setup links table, for example Pending, In progress or Completed.

Note

Credentials go straight into an encrypted vault. Your group sees the data, never a password or a key, and the contact can revoke access from the tool itself at any time. See the privacy policy and DPA for where data lives.

Check that the first sync worked

6

Watch the first sync, then check a number you know

The first sync starts by itself within a few minutes of connecting, and after that every 24 hours. Change the rhythm under Schedule on the source's page, from every 5 minutes to daily or manual.

Sources shows each connection's status. Connected and Syncing are what you want. Error or Reconnect needed means a sync failed or access ran out; open the source to see why. Entities rolls this up per company: Healthy, Needs attention, and Stale when nothing has synced in 48 hours.

Then compare one figure you already trust, such as last month's revenue for one company, with what Gatlas shows. A match is the quickest proof the connection is right.

Shape the data into views

Synced data arrives as each tool stores it. A view turns it into a dataset that answers a question, such as monthly revenue by company, with a description an AI assistant can read. Stripe and PostHog come with starter views. For everything else you build the views your questions need, and you do not need to write SQL to do it.

7

Create a view

Pick whichever suits you:

  • Ask Claude. Once you have connected it with a read/write MCP connection (steps 10 and 11 below), describe the dataset you want; Gatlas builds and publishes the view, usually in under a minute. The view-builder skill on Skills walks you through it.
  • In Views, choose Create view and use the Visual builder or the SQL editor.
  • In the SQL workspace, Run a query and Save as... a view.

More on this in Views and SQL.

8

Describe it and publish it

Give each view AI context: what a row is, what the numbers mean, and what to watch out for. Then turn on Publish to MCP. AI assistants only see published views, so this is the switch that makes a view answerable.

Give people access

9

Invite your team

Under Settings, Members, choose Invite member, enter an email address, pick a role and the companies they can see: All companies, or Specific companies (each one checked, plus everything under it). The roles:

  • Member: explores all data, runs syncs and uses the MCP connections an admin creates.
  • Admin: full control of sources, views, documents and members.
  • Principal: an admin who can also add and remove admins in their companies.

You can invite anyone to a role below your own. Owner is not offered: the person who created the organization is its owner. The invitation is emailed, and the link is also copied so you can send it yourself.

10

Connect people's AI assistants

On MCP, choose New connection. Name it after the person or the tool, choose Read-only or Read/write, and turn on Scoped access to limit it to certain companies or views. Create gives you a Setup link for recipient, valid for 30 days, which walks them through adding Gatlas to Claude, Cursor or another AI assistant in about a minute.

Important

New connections start as Read/write, which lets an assistant create views and change settings within its scope. Choose Read-only for anyone who only asks questions.

Ask the first questions

11

Connect Claude and ask

Create a connection for yourself as in step 10 and copy the key it shows. In Claude, open Settings, Connectors, Add custom connector, paste the server URL https://www.gatlas.ai/api/mcp (with the www) and choose Add. Choose Connect, paste your key on the Gatlas page that opens, and choose Authorize. The full steps for each assistant are in Using your MCP connection.

Then ask what you wrote down at the start. For example:

  • "What was revenue by company for each of the last six months?"
  • "Which invoices are more than 60 days overdue?"
  • "Which views can you see, and what does each one answer?"

On Skills, Copy prompt gives you ready-made finance workflows, such as a monthly P&L, a portfolio rollup or cash flow, to paste into Claude.

You are onboarded when the checklist is done

Admins see the same list as a Getting started checklist on Entities, ticked off as the work happens:

  • Create an entity
  • Connect a data source
  • Run your first sync
  • Add AI context
  • Create a view
  • Publish a view to MCP
  • Share MCP access
  • Delegate a setup link

The real test is simpler: someone who was not part of the setup asks Claude a question about the portfolio, and the answer matches your books.

Your first month

Most groups settle into a rhythm like this. Nothing here waits on anyone from Gatlas; the timing is yours.

  • Day one: sign up, build the company tree, and send a setup link to each company's contact.
  • The first week: the setup links come back, the first syncs run, and you check one number per company against its books.
  • The second week: build the views your first questions need, describe them, and publish them.
  • The rest of the month: invite the people who ask questions, connect their AI assistants, and turn on Slack alerts. By then the checklist above is done.

Keep it healthy

Under Notifications, pick a company and choose Connect Slack. Its alerts tell a channel when a sync fails, a connection goes stale or access is about to expire, so a broken connection gets fixed before anyone asks a question it cannot answer.

Get help

Write to team@gatlas.ai or use Feedback in the app's sidebar. We usually reply within a business day. A missing connector, a number that does not match, or a question the docs do not answer are all worth an email.