Give your team a seat by email. Take it back in 30 seconds.
The Team view lists every person who can open your numbers, the role beside each name, and the seats you have left. Add someone with an address. Remove them, and their access ends within 30 seconds.
How many people can I give a seat?
As many as your plan carries: three on Starter, three on Launch, ten on Growth and unlimited on Command. The top of the Team view reads seats used of seats on your plan, and a badge beside it repeats the count. Fill the plan and the badge changes colour, a line appears that says Seat limit reached and points you to Billing, and the next press of Invite tells you the same thing. Nothing fails quietly.
The count comes from your plan record, not from a number typed into your page. The plan name and the seat count on this view are read from the same record the sign-in page and the seat check read, so the Team view, the Billing view and the door itself agree on one number.
Our team never takes one of your seats. A TruLata address opens your dashboard as the operator and spends nothing against your plan, so every seat you pay for is yours to give.
Export the list when you need it. The Members table downloads as a CSV with four columns: name, email, role and status.
How do I add someone?
Type their email, pick Member or Admin, press Invite member. The row appears in the Members list marked Invited and the seat count moves. The seat is recorded against your plan with four things on it: the address, the role, who invited them and when.
A full plan refuses the record instead of stretching the count. The refusal says seat limit reached and gives the numbers, so the count on your screen and the count on ours are always the same number.
The new person signs in with a link, not a password. They open login.trulata.com, enter their address, and a plain-text email from TruLata arrives with the subject line Your TruLata sign-in link. The link works once and expires in 15 minutes. Hold a seat on more than one account and the link lands on a chooser that lists each account by name.
The sign-in page answers the same way whether or not an address holds a seat, so nobody can use it to find out who works at your company. A link that has expired or already been used says so and offers a new one.
Your Owner seat is named by our team in week one of setup, with the rest of your access. From then on the Owner, or any Admin the Owner names, adds the team.
What can each role do?
Every seat opens every view your account carries. Member, Admin and Owner read the same numbers; the role decides who can change the team, not what they can see.
Only an Owner or an Admin can invite or remove a teammate. An Admin can grant Member or Admin, and cannot remove an Owner. Nobody can remove themselves. The last Owner cannot be removed until another Owner is named, so an account can never lock itself out.
The Owner seat is also the one the screen never offers to remove. Billing and plan changes on a live account go to your TruLata team as a logged request from the Billing view, so a plan never changes because someone pressed the wrong control.
Every seat action is logged with the address that made it: invited, revoked, or refused and why. That is the audit you can hold us to: who asked, for whom, and when.
How fast is someone out once I remove them?
Within 30 seconds. Remove a seat and every request from that address gets a refusal page instead of your numbers. The page says the address is signed in but does not hold a seat on this dashboard, and tells them to ask the account owner. It covers the data file the page draws from as well as the page, so a removed address cannot fetch your numbers by a side route.
The 30 seconds is a cache, stated so nobody assumes instant. One page load is a dozen requests and each is checked against the seat list, so a decision is held for 30 seconds rather than asked a dozen times. A removed seat can keep working for up to 30 seconds on a decision already made. Not a day, and not a ticket to a vendor.
A removed seat is kept, not deleted. The record stays with the status revoked, so the question an audit asks, who held a seat and when, still has an answer. It stops counting against your plan the moment it is revoked, so the seat is free for the next person straight away.
Removal needs no edit at the edge and no redeploy. The seat list is what authorises, so a revoked address is refused whether or not any access rule elsewhere still names it. If our seat service does not answer within two seconds, a person already past the sign-in gate stays in and the decision is logged; a revoked seat working a few minutes longer during an outage is the smaller failure than locking you out of your own numbers.
What does this look like across a month?
Say you run four crews and an office of two, and you hold the Owner seat. On Monday you give your office manager a Member seat so she can open Leads each morning and mark the weekend's two spam submissions as not a lead. On Tuesday a freelancer building your spring campaign needs the numbers for six weeks, and you add her as a Member. Each invite is one press, and each is recorded with your address as the person who made it.
For six weeks they open the same dashboard you do, on their own addresses. There is no password of yours to share, and nothing of yours to reset when the work ends. Neither of them can touch your ad account, your CRM, your website or your Business Profile from the screen, because no seat has a write path to them.
When the campaign ships, you remove the freelancer's seat. Within 30 seconds her next request for your dashboard is refused, the record keeps her seat as revoked, and the seat is free for the next person. Your office manager never notices.
Nothing on this view runs on a schedule. Seats change when a person changes them. The scheduled work sits elsewhere: the ads change watch reads your ad account every morning at 7:05am ET, the nightly bake writes your fallback snapshot at 12:01am Central, and once an hour a job checks that your dashboard's seat pin, its registry row and its live access application still agree.
What should I check in the demo?
Open demo.trulata.com and go to Team. Read the seat line at the top and the count badge beside it. Type an address, pick a role and press Invite member: the row appears in Members marked Invited and the count moves. Press Remove beside a name and the count moves back. Read the Roles card. Every number on the demo is illustrative, and the engine is the same code every client runs.
Then read what is not on this screen. There is no password field, because sign-in is a link. There is no control that writes to your ad account, your CRM, your website or your Business Profile, because no seat has one. Your email inbox, your calendar and your customers' card data are not connected on any instance, so no seat can reach them either.
Then ask for the ledger. Every seat record names who invited whom and when. Every removal is kept as a revoked record. Every seat action is logged with the address that made it, and every fail-open is logged. Ask for any of those rows on your account and we can show you the row.
The Team view, in one table.
| What | Where it comes from | How fresh |
|---|---|---|
| Seat count | Seats used of seats on your plan, read from your plan record | Every open |
| Invite | Email plus role; the seat is recorded with who invited them and when | Logged with the sender's address |
| Sign-in | Single-use link from login.trulata.com | Works once, expires in 15 minutes |
| Roles | Member or Admin, and one Owner | Recorded on the seat |
| Remove | Refusal page for the address; record kept as revoked | Effective within 30 seconds |
| Passwords | None; sign-in is the link | Never stored |
| Export | Members as a CSV: name, email, role, status | Any time |
Every sign-in is a single-use link to the address on the seat, so there is nothing to share, nothing to reset and nothing for us to store.
Questions, answered.
How many seats do I get?
three on Starter, three on Launch, ten on Growth and unlimited on Command. The Team view shows seats used of seats on your plan, and says Seat limit reached when the plan is full.
How does a new person sign in?
With a single-use link sent to their address from login.trulata.com. It works once and expires in 15 minutes. There is no password.
What can an Admin do that a Member cannot?
Invite and remove teammates. Both read every view your account carries. An Admin can grant Member or Admin, and cannot remove an Owner; only an Owner can remove an Owner, and the last Owner cannot be removed.
How quickly is someone locked out after I remove them?
Within 30 seconds. The decision is held that long so a page load does not ask the seat list a dozen times, and that hold is the whole delay.
Can a team member change my ad account or CRM from the screen?
No. No seat has that write path, because the product does not have one.
What if my plan is full?
The view says Seat limit reached and points you to Billing, and the next invite is refused with the numbers. It does not fail quietly.
Does your team take one of my seats?
No. A TruLata address opens your dashboard as the operator and spends nothing against your plan.
Can I see who invited someone?
Yes. Each seat record carries the address, the role, who invited them and when, and a removed seat stays on record as revoked.
See it running
before you decide.
The demo is the real product on a fictional company, with no form in front of it. Pricing is three published tiers. Setup on your own accounts takes two to four weeks.
Open the live demo See pricing
New here? See what the Command Center is. Prefer to write? Send us the one thing you want to know.
- Refreshed when you open itLive data on page load, never a monthly PDF
- Counted from your own formsLeads recorded server-side, compared daily with Ads and GA4
- Four answer engines, measuredChatGPT, Gemini, Claude and Grok, with a published denominator
- A review-first queue on every sendEvery draft waits in a review-first queue and every send is logged.