Team members & viewing a client’s account
You don’t have to run your reseller account alone. You can bring on team members to help manage clients day-to-day, and grant each of them exactly the additional permissions they need — viewing a client’s account, revoking access instantly, replying from a specific inbox address, or sending campaigns — without ever handing over your billing, domain, or pricing controls.
Adding a team member
From White Label settings, invite anyone by email. They’ll get an invite link; accepting it links their own BlnkSpace account to yours as a team member — no separate login, no shared password.
Enter their email under “Team members.” Only you (the account owner) can do this — it’s not something a team member can do on your behalf, even after they’ve joined.
They open the link, signed in as themselves (or create an account if they don’t have one). If they’re already signed in as a different BlnkSpace account than the one you invited, they’ll be told to switch before it’ll accept.
Once accepted, the White Label section appears in their sidebar too — showing your client list and settings, not a separate account of their own.
Every new team member starts with the baseline permissions only (see below) — every extra permission is off by default and granted per person, per toggle. Nothing is bundled: giving someone the ability to view a client’s account doesn’t also let them manage campaigns, and vice versa.
Every team member gets the same routine, everyday baseline. On top of that, you choose — person by person — which of the higher-stakes permissions they also have:
| Action | You (owner) | Team member |
|---|---|---|
| Invite / view clients | Yes | Yes |
| Remove a client (keep access until their paid period ends) | Yes | Yes |
| Remove a client immediately | Yes | If granted |
| View a client’s account (see below) | Yes | If granted |
| Reply/send from a Domain Inbox address (see below) | Yes | If assigned |
| Create/send campaigns (see below) | Yes | If granted |
| Manage products & categories (see below) | Yes | If granted |
| Manage orders — fulfillment, refunds (see below) | Yes | If granted |
| View & manage Paid Pages — buyers, revoke access (see below) | Yes | If granted |
| Manage the CRM — pipelines & deals (see below) | Yes | If granted |
| Manage Booking — availability & bookings (see below) | Yes | If granted |
| Manage Automations — build & edit rules (see below) | Yes | If granted |
| Manage Events — create events, attendees (see below) | Yes | If granted |
| Invite or remove team members | Yes | No |
| Create a new domain email / sender identity | Yes | No |
| Connect/disconnect Stripe or Resend | Yes | No |
| Create, price, or disable a Paid Page offer | Yes | No |
| Resale pricing, app domain, brand name/logo | Yes | No |
Viewing a client’s account
Sometimes the fastest way to help a client is to see exactly what they’re seeing. From your client list, “View as” opens a real, working session as that client — their documents, their settings, their view of the product — without needing their password.
| Who can do this | You (the account owner) always, plus any team member you’ve individually granted this to — it’s off by default for every new team member. |
| Which clients | Only someone currently on your own client list — this is re-checked at the moment you click, not assumed from anything cached. |
| How long it lasts | Up to 30 minutes, or 10 minutes of inactivity, whichever comes first — then you’re automatically signed back out of their account. |
| How to tell you’re in it | A banner stays visible the entire time you’re viewing as them, with an Exit button to leave whenever you want. |
Every time this is used, it’s recorded — which client, and which real person on your team did it — so there’s always an honest record of who looked at what, even though there’s no in-app screen to browse that history yet.
Revoking a client immediately
Removing a client normally lets them keep access through whatever they’ve already paid for. “Revoke immediately” skips that grace period and cuts access instantly — meant for abuse or confirmed non-payment, not routine offboarding.
| Who can do this | You always, plus any team member you’ve individually granted this to. |
| When it’s actually available | Only once a client has been genuinely past-due on payment for a few days — the button stays disabled until then, for you and any granted team member alike, so nobody can use this on a whim. |
Domain Inbox address access
Your Domain Inbox can receive at more than one address — help@yourdomain.com, orders@yourdomain.com, whatever you’ve set up. You can assign a team member to exactly one of those addresses, or several, and they’ll only ever see, reply to, and send from the ones you’ve assigned — nothing else on the account.
A brand-new team member sees an empty Domain Inbox until you assign them at least one address — this is the same “off unless granted” default as every other team-member permission.
You pick from the addresses that actually exist on your account — there’s no free-text field, so a team member can’t end up assigned to something that isn’t real.
Threads, the address filter, replying, and composing a new email are all scoped to exactly the address(es) you’ve assigned — a team member assigned to help@ never sees or sends as orders@, even if they know it exists.
Campaign management
Letting someone send campaigns is a different kind of decision than letting them reply to a customer — a campaign can reach your entire contact list in one send. That’s why it’s its own separate permission, not something a team member gets automatically just because you’ve assigned them a Domain Inbox address.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default, and independent of every other permission on this page. |
| Which contacts | Your real contact list — a granted team member creates and sends campaigns to the same contacts you’d see yourself, not a separate list of their own. |
| Which sender address | Whichever Domain Inbox address(es) you’ve separately assigned them — a team member with campaign access but no assigned address can’t send a campaign until you assign one. |
| What they can’t touch | Adding, importing, or deleting contacts stays yours to manage — a granted team member can send to your existing contacts, not manage the contact list itself. |
Product management
A team member with this granted can reach your Product CMS — creating and editing products, managing categories, and syncing variants to Stripe — as if it were their own catalog, but everything they touch reads and writes against your account, never theirs. This also lets them view orders (read-only) — actually fulfilling or refunding one needs the separate Order management permission below.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default. |
| What they can do | Create/edit products, manage categories, sync variants to Stripe, view orders — all against your catalog. |
| Which domain a new page publishes to | If you’ve set up more than one website/domain on your account, a granted team member sees a picker when publishing a product with no category selected, so they can choose the right one instead of it guessing. You can optionally restrict a specific team member to specific domains. |
Order management
A separate permission from Product management, on purpose — editing a product listing and moving real money (fulfilling an order, issuing a refund) are different levels of trust. A team member can have one without the other.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default, independent of Product management. |
| What they can do | Mark orders fulfilled/shipped, issue refunds — real Stripe money movement, gated separately from catalog edits. |
| Without this permission | A team member with only Product management can still see every order (read-only) but has no fulfillment/refund controls. |
Paid Pages access
Paid Pages is where you see who’s bought or subscribed to your gated content, and revoke access if needed. Granting this lets a team member see that same dashboard for your account.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default. |
| What they can do | See your gated pages, buyer/subscriber lists, and revoke a specific buyer’s access (this also cancels a live Stripe subscription, same as when you do it yourself). |
| What they can’t do | Set up a new Paid Page, change its price, or turn Sell access on/off — those stay owner-only, same boundary as Stripe/Resend above. |
CRM management
Lets a team member reach your CRM Pipelines — creating and editing deals, adding custom fields, dragging deals between stages — same as their own board, but everything they touch belongs to your account.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default. |
| What they can do | Create/edit pipelines, stages, and deals; add custom fields; move deals; see contact lifetime value. |
Booking management
Lets a team member manage your Booking Calendar — availability, appointment settings, and the bookings themselves.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default. |
| What they can do | Edit weekly hours and date overrides, appointment length/buffer/timezone, approve or decline pending bookings, cancel bookings, mark no-shows. |
Automations management
Lets a team member build and edit the "when X happens, do Y" rules on the Automations page — for CRM, Booking, Orders, and every other source at once, not split up per feature.
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default. |
| What they can do | Create, edit, enable/disable, and delete automation rules, including the four built-in system automations (order/shipping/booking confirmation, booking reminder). |
Events management
Lets a team member create and manage Event blocks — a separate permission from Booking, even though both are scheduling-adjacent, since they’re genuinely different features (one owner-published event vs. a 1:1 calendar).
| Who can do this | You always, plus any team member you’ve individually granted this to — off by default. |
| What they can do | Create/edit events, manage attendee lists, cancel events and individual RSVPs. |
If someone is on more than one team
It’s possible for the same person to be a team member for more than one reseller account at once — helping two different agencies, for example, or being staff for one account while also running their own separate BlnkSpace products elsewhere. When that’s the case, Products, Paid Pages, and Campaigns each show a small “Acting as” switcher at the top of the page so they can pick which account’s data they’re currently looking at — and their own account is always one of the choices, listed as “Me,” never just left out in favor of the accounts they help manage. If someone only works with one account — true for almost everyone — this switcher doesn’t appear at all, and nothing about their experience changes.