Sharing your account with a colleague — Help

If you run events with a colleague, you've probably wanted a second pair of hands inside the same 1pm account: someone who can build events, edit the run of show, manage contacts, and send share links alongside you, without you handing over your password. Account sharing does exactly that. You grant a colleague admin access as a paid seat on your subscription, and they work inside your account as you, while your billing and account settings stay yours alone.

This is the step-by-step on how to share your account, what a collaborator can and can't do, and how to take access back. For the wider picture of how teams and agencies organise themselves around 1pm (and where full multi-user workspaces are headed), see Working with a team.

Who you can share with

A few ground rules before you start:

The person you invite doesn't need a subscription of their own. You fund their seat, which is what makes them a member of your account rather than a second customer. If they're not on 1pm at all yet, the invite email walks them through setting a password; if they already have an account, the same link sends them to sign in and accept.
Each person who accepts is added to your subscription as a paid seat, billed pro-rata from the day they join. Before an invite can go out you have to tick the box on the form acknowledging that, and the invite is refused server-side without it. Extra users are free while you're on a trial.
They must have verified the email address on their own account before they can accept. Accepting is what proves they control the address you invited, so an unverified sign-up can't claim someone else's email and pick up admin access. If they try to accept before confirming, they'll be prompted to check their inbox for the confirmation link first.
Your own account has to be in good standing (trialing, active, or complimentary) at the moment they accept. You're paying for the seat, so a lapsed subscription on your side is what blocks it, not anything about theirs.
You invite by email, and the invite stays pending until that person accepts. Nothing happens to your account until they do.
There's no limit that stops you working: you keep full ownership throughout. Sharing adds an admin, it doesn't hand the account over.

Two caps sit behind all of this. One account can have 25 people with access at a time, which is well past any realistic venue or planning team. And while you're still on a trial you can invite only a couple of teammates, so a trial stays an evaluation rather than a free team deployment; the page tells you the number if you hit it, and the cap lifts the moment you add a payment method on the Billing page.

Inviting someone

Open the account menu and go to Team. Under "People with access to your account", type the colleague's email, tick the box confirming you understand the per-seat charge, and click Send invite.

The invite then shows in your list with an "Invitation sent" badge until they accept, at which point it flips to "Has access". If you invited the wrong address or change your mind before they accept, the same row has a Cancel button (it reads Revoke once they've accepted).

Accepting an invite

If someone has shared their account with you, open your own Team page. Under "Accounts shared with you" you'll see their account with an "Invitation pending" badge and Accept and Decline buttons. Accept, and the badge flips to "You have access". (You'll need a verified email address of your own, and their account has to be in good standing, since they're the one funding your seat. If either isn't true yet, the page tells you what to fix.)

From then on, that account appears in the same list with an "Open account" button. Click it to switch into their account and start working. While you're switched in, the account slot in the top bar reads "Working in" their name, with an Exit button beside it to come straight back to your own. Everything you do happens under their account: events you create are theirs, crew links carry their branding, history is theirs.

What a collaborator can do, and what stays yours

A collaborator has full admin over the working parts of your account. They can create and edit events, edit timelines, add and edit contacts and spaces, send and review requests, set branding, and manage your custom fields. They can do anything you can do with your event data, including deletes, so share with someone you trust accordingly.

What stays locked to you, the account owner, even while a collaborator is switched in. These are blocked outright: going at the URL directly returns a refusal rather than the page.

Managing who has access. The Team page itself, so they can't invite other people or revoke anyone.
Two-factor authentication on your login.
Account deletion. Only you can delete the account.
Exporting your data, which is the whole account in one ZIP.
Online payments (your Stripe payout account) and your Xero connection.
Your sending domain, and confirming a change to your email address.

Two surfaces sit in between rather than being blocked. The Billing page opens, but the subscription card and the owner-only cards are hidden and the button through to the Stripe portal refuses. And your profile page opens too, because most of what's on it is operational rather than personal: a collaborator can set the display name, the run-of-show and crew wording, and the default Space. Only your password and your email address are hidden there, and their handlers refuse as well, so those can't be changed behind your back.

In short: they manage the work, you manage the account, your money, and your login.

Revoking access, or leaving

Either side can end the arrangement at any time:

As the owner, open Team and click Revoke next to the person's name.
As a collaborator, open Team and click Leave next to the account.

Access is re-checked on every request, so revoking or leaving takes effect immediately, not at the next sign-in.

The same check covers your subscription, and it looks at yours only. Because you fund every seat, an owner account that stops being in good standing suspends all of its collaborators on their next click, and they drop cleanly back into their own account. A collaborator's own billing has nothing to do with it; they're not expected to have a subscription at all.

A note on what this is and isn't

Account sharing is one shared account with a second admin. It is not (yet) a full multi-user workspace: there's still a single subscriber and a single profile, and edits aren't individually attributed to one person or the other, so you can't see "who changed this timeline item". Email is the one exception: every send is stamped with the person who actually sent it, so the "Sent by" column in the email Activity log does tell you which of you emailed a client or a crew member. If you need per-person sign-ins with their own audit trail, finer-grained roles, or many independent users under one roof, read Working with a team for the patterns that fit those shapes today, and let us know at [email protected], since that's the kind of signal that shapes what we build next.

Working with a team covers the bigger picture: how agencies and venue operations teams organise around 1pm, and where multi-user is headed.
Your profile and display name covers changing the email and password on an account, which is the route for handing an account between people rather than sharing it.