For teams
Roll out to the whole company in a day.
Not a quarter-long IT project. Connect your domain, lock the brand once, and every employee's card looks and behaves exactly the way it should — before lunch.
Rollout
Four steps, one afternoon
- Step 1
Connect your domain
Verify your Google Workspace domain and turn on auto-join — anyone who signs in with a company email lands in your org automatically, no invite needed.
- Step 2
Invite the rest — bulk CSV import is coming
Contractors, shared accounts, anyone outside the domain — invite them individually today and apply your locked template by hand. Bulk CSV import (names, titles, departments pre-filled onto the template) is on the roadmap, coming with org-managed card provisioning.
- Step 3
Lock the brand once
Set the logo, accent color, and required fields at the org level. Every card that gets created after this point inherits it automatically.
- Step 4
Everyone has a card
No app install for the people they meet, no separate rollout for a new hire — they sign in and their card already looks right.
One brand, everywhere it shows up
Logo, accent color, and required fields are set once at the org level and locked — a member can personalize what you leave open, but the fields you lock (company name, logo, legal entity) stay consistent on every card, every event, without anyone needing to remember to set them right.
De facto standard
Once the first team adopts it, new hires and other teams find their own card already waiting.
Brand-locked templates
Locked fields can't be overridden on a member's card — brand consistency isn't a policy doc, it's the schema.
Analytics per event
Shares, saves, and follow-up completion roll up per event and per org in the console.
Offboarding
Offboarding keeps your data
No competitor we reviewed foregrounds what is and isn't revocable after someone leaves. Cardinal publishes it as a trust asset during IT eval, not a support ticket after the fact.
Access revokes immediately
When someone leaves your org, their session and server-side profile are revoked the moment you remove them — no lingering login.
Org data stays with the org
Contacts, meeting summaries, and follow-up history they created on the job stay in your org's export, searchable by whoever inherits their pipeline.
Written, before you sign
A documented pilot/offboarding protocol is provided at signup — what's revocable and what isn't, in writing, not discovered after someone's already gone.
See it work for your org
Bring your seat count and your rollout timeline — we'll walk through the console, the brand lock, and the export/offboarding policy live.
Talk to us