Workspaces and Tables

Outcome: a workspace set up for how your team actually works, a naming convention written down, and a clear rule for when something deserves a new table.

Surface: Sync GTM app
Level: Beginner
Uses: Workspace settings
Credits: 0
Prerequisite: A Sync GTM account

The two containers

Container	Holds	Shared across it
Workspace	Tables, integrations, members, API keys	Credits, connected accounts, permissions
Table	Rows and columns for one piece of work	Nothing — tables are independent

A workspace is a billing and access boundary. A table is a unit of work. Most teams need exactly one workspace and many tables.

Full reference: Workspaces and Tables.

When to create a second workspace

Only for one of these reasons:

Separate clients. An agency running lists for three customers needs their data and integrations apart.
Separate credit budgets. Marketing and sales each want to see their own consumption without arithmetic.
Different CRM connections. Two Salesforce instances cannot both be the default in one workspace.

And not for these:

Different campaigns — that is a table.
Different segments — that is a table, or a view.
Testing versus production — that is a table with ten rows.

Credits do not move between workspaces freely, and integrations must be reconnected in each. Splitting early is the setup decision people most often regret. Start with one.

Naming, so you can find things later

A workspace with forty tables named “Test”, “Test 2” and “final list” is a workspace nobody can audit. Use a pattern and stick to it:


<motion>-<segment>-<grain>-<yyyy-mm>

outbound-uk-fintech-companies-2026-08
outbound-uk-fintech-people-2026-08
signals-hiring-watchlist-companies
crm-repair-stale-contacts-2026-q3

Three properties make this worth the effort: it sorts sensibly, it tells you the grain without opening the table, and it makes the difference between a standing table and a one-off run obvious.

One table per grain

This is the rule that saves the most rework, and it comes straight from GTM Engineering lesson 02.

Company work goes in a company table

One row per company. Sourcing, firmographics, tech stack, signals, scoring.

Person work goes in a person table

One row per human, built from the qualified companies. Contact details, titles, personalization, export.

Never mix them

A table with contact_1_email, contact_2_email, contact_3_email is a person table wearing a company table’s clothes. It exports badly, filters badly, and cannot answer “how many contactable people do we have?”

The two tables are linked by the company domain — the match key from the same lesson. Keep the domain column in both.

Members and permissions

Invite people at the workspace level. Two practical notes:

Anyone who can run a column can spend credits. There is no per-user cap, so treat workspace membership as budget access and keep a shared table of who ran what if the team is larger than a few people.
Integrations are workspace-wide. Connecting your CRM once makes it available to every member and every table — which is convenient, and worth knowing before you connect a production Salesforce.

Do this now

Confirm your workspace

Open workspace settings. Check the name is something a colleague would recognize, and note the credit balance.

Write your naming convention

Pick the pattern above or your own. Write it somewhere the team can see — a pinned doc, a table description.

Create the course table

Name it 101-<your segment>-companies-<year>-<month>. Leave it empty; lesson 04 configures it.

Decide the second table now

You will need a person-grain table by lesson 07. Decide its name now so the pair stays consistent.

Check your work

You have one workspace, unless you can state which of the three reasons applies
Your table name says motion, segment, grain and date
You have not created a second workspace for testing
You know your current credit balance

Where this breaks

The mistake that costs a week is discovering at lesson 11 that your company table has three contact columns bolted on. Every export from that point mangles the second and third contact, and fixing it means rebuilding the person side from scratch. Decide the grain before the first row lands — it is free now and expensive later.

Further automation

Once a table shape works, save it as a Template so the next segment starts from a configured table rather than an empty one. Teams that do this go from an afternoon per list to about ten minutes.

Next lesson

04 — Your first table, configuring the columns before any data arrives.

Reference for this lesson: Workspaces, Tables, API keys, Credits.