Team Access
Team access lets a colleague or an outside contractor into your dashboard without you sharing your password.
Open the account menu and choose Invite teammate.
Sending an invite takes 49 seconds on video:
How it works
You mint a link, and whoever opens it is signed into your dashboard as a guest with the role and the expiry you chose. They have no account to create and no password to remember.
It is fast, but it is not a full user-management system: every guest acts as you, with no record of which person did what. Read the limits below before you use it for something long-lived.
Creating an invite
| Field | Options |
|---|---|
| Role | Marketing, Developer, Admin |
| Duration | 24 hours, 7 days, 30 days, or never expires |
| Website | One site, or all of them |
| Emails | Optional. One or more addresses to label the invites |
Create, and you get a link per email. Send it however you normally send things.
Roles
- Marketing. For the person who owns content: conversations, content gaps, snippets, starter questions.
- Developer. For the person doing the install: widget setup, install, API keys.
- Admin. Everything.
Duration
Match it to the job. A contractor doing an install needs 24 hours, not forever.
Never expires exists for a permanent teammate. Use it deliberately and revoke it when they move on.
The link is the credential
Anyone holding it gets in. There is no second factor and no email check on the way through.
That has a few practical consequences:
- Send it over something private. Direct message or email, not a shared ticket or a public channel.
- Do not paste it into a document that gets forwarded.
- Prefer a short duration. It is the cheapest safety net available.
- Revoke it the moment the work is done.
Managing invites
The same modal lists active grants: label, role, website scope, expiry, and when it was last used.
Revoke kills a link immediately, mid-session if someone is using it.
Review the list every few months. Grants with no expiry and no recent use are the ones worth removing.
Limits worth knowing
- Guests act as you. Actions they take are attributed to the account, not to them. There is no per-person audit trail.
- Guests cannot manage billing, and they cannot mint more invites.
- Expiry and revocation are the only controls. There is no way to change a live grant's role. Revoke and issue a new one.
If you need named users with individual logins and an audit trail, tell us what you need. Contact us.
Alternatives worth considering
A tool that needs API access. Do not use an invite link. Create an API key named after the tool, or connect it through OAuth. Both are revocable independently and neither gives anyone dashboard access.
Someone who only needs the numbers. Export what they need rather than granting access. Searches export as CSV and billing history as a file, while conversations export one thread at a time.
A permanent colleague on a shared team. A shared login with two-factor is more honest than a never-expiring guest link, because at least everyone knows what it is.
Checklist
- [ ] Shortest duration that covers the work
- [ ] Narrowest role that covers the work
- [ ] Scoped to one website when that is all they need
- [ ] Sent over a private channel
- [ ] Revoked when the work is finished