Creating a customer workspace, end to end
A workspace is created by signing in, not by filling in a form. The first Google sign-in from an address with no existing membership creates three rows together: the workspace, your membership as its administrator, and its entitlement with a starting plan. Nothing can arrive yet — a workspace with no connected mailbox and no claimed number has no way in.
What the first sign-in creates#
Signing in with an address that already administers a workspace does not make a second one; you are returned to the workspace you already have. That check comes first for a good reason — an accidental second workspace is an empty product with none of your history in it, and the confusion it causes lasts long after the mistake.
| Record | What it carries | Why it matters later |
|---|---|---|
| The workspace | A stable identifier, a name, a kind and an active status | Every business record from now on carries this identifier and is filtered by it three separate times |
| Your membership | You, in that workspace, as its administrator | Membership is what a session resolves through; without it there is nothing to sign in to |
| The entitlement | A starting plan, its daily limits, and a required signature line | This is what allowances are measured against, and what a paid activation later replaces |
Stage by stage#
- Trigger — somebody chooses to continue with Google using an address that administers no workspace yet.
- User or external event — Google's own consent screen. Connect never sees a password, because there is no password to see.
- Authentication and workspace resolution — the platform person is ensured first, then their memberships are checked. An existing administrator membership ends the flow here by returning the workspace they already have.
- Ingest or request — the sign-in callback continues in one transaction, so a workspace never exists without the membership and entitlement that make it usable.
- Canonical record — the three rows above. No mailbox, no number, no contact, no knowledge: an empty workspace is genuinely empty.
- Reasoning — none. Nothing is decided about the business at sign-up, and nothing is inferred from the address beyond what it is used to name.
- Knowledge, memory and rules — created empty rather than pre-filled. Every memory tier answers 'nothing is set here', which is a visible answer rather than a missing one.
- Autonomy and approval — the workspace starts with rules that ask before acting. A new workspace does not begin sending on its own the moment a mailbox is connected.
- Action through a provider — only Google, and only for identity. No mailbox is connected and no number is claimed by signing in.
- Result — a session carrying exactly one workspace, and a first screen that is honestly empty.
- Relationship, timeline and memory — nothing is written to any relationship. You are a member of the workspace, not a contact in it.
- Audit, usage and Needs You — the sign-in is recorded, no allowance is spent, and the setup work that remains is what the first screen is for.
Three things still missing#
Connect a mailbox — Google, Microsoft, or any IMAP and SMTP server.
Result Mail can be fetched. How many mailboxes may be connected at once is a plan ceiling rather than a daily allowance, so it is checked when you add one, not when mail arrives.
Give the workspace something to be grounded in: what the business does, what it sells, how it answers.
Result Replies stop being generic. A workspace with no knowledge produces answers that are polite and useless, which is worse than no answer.
Decide what Connect may do on each channel before turning it on.
Result The first days are visible: drafts you approve rather than sends you discover afterwards.
Phone is separate again: a workspace can receive mail without ever claiming a number, and a number is proved to belong to a workspace by a record inside it rather than by anyone typing the digits in. Until that record exists, an inbound call has no workspace to belong to.
What the starting plan changes#
A new workspace has real daily limits from its first minute — they are not switched on later. The other visible difference is the signature line the starting plan requires on outbound mail; a paid activation replaces the entitlement wholesale, which is what removes it along with raising the allowances.
None of this affects what the workspace may do. Every capability is present on day one, over the same implementation the operator's own workspace uses — the difference is volume, and volume alone.
Questions#
Can I have two workspaces on one Google address?
Not by signing in twice — the existing administrator membership is found first and returns the workspace you already have. Being a member of more than one workspace is possible, but a session resolves to exactly one of them at a time.
Does creating a workspace connect my email automatically?
No. Connecting a mailbox is a deliberate, separate consent, and until it happens nothing can arrive. A new workspace with an empty inbox is behaving correctly, not failing quietly.
Is anything shared with other workspaces?
No. Every business record carries the workspace identifier and is filtered by it in the middleware allowlist, in the query layer and again by the database itself. A record without that stamp is invisible rather than shared.