Part 1: Members, with the job they do
Everyone who can reach the workspace, in one list, with what each of them is allowed to do visible rather than buried.
Your crew
Team access, roles and door staff
The person scanning tickets at the door does not need to see your bank details.
A Verimly workspace has members, each with their own permissions across events, tickets, orders, customers, analytics, settings, billing, team and point of sale. Event-night crew are separate: personnel sign in with a PIN on a device that has been paired to your workspace, so a shift change takes four digits and a lost phone can be revoked without changing anyone's password.
What you are looking at
The numbers on the screen above mark the parts that do the work. Here is what each one is.
Part 2: Permissions by area
Events, tickets, orders, customers, analytics, settings, billing, team and point of sale. Each is granted on its own, so access matches a real job.
Part 3: Invite by email
An invitation rather than a shared login. People join with their own account, and leaving is one removal instead of a password change for everyone.
Part 4: Door personnel and PINs
Event-night crew get a PIN, not a workspace account. Fast at the door, and it does not hand a volunteer the keys to the business.
Part 5: Paired devices you can revoke
Each POS device is paired once and can be unpaired from here. A phone left in a taxi stops being a box office.
In practice
Access that matches the job
A promoter needs to publish events. A bookkeeper needs orders and billing. A marketing freelancer needs analytics and nothing else. Because each area is granted separately, you can describe a real job rather than choosing between "admin" and "can barely do anything".
- Publishing is its own permission, so someone can build an event without being able to put it on sale.
- Billing and payouts sit behind their own permission and are not part of everyday access.
Door staff are not accounts
The person on the door for one night should not need a workspace login, an email invitation or a password reset at eight in the evening. They need a four-digit PIN on a device you already trust. Personnel are managed separately from members for exactly that reason.
- PINs can be changed or removed after an event without touching anyone else.
- What personnel can do — sell, scan, or both — is set per person.
Devices are trusted, not just people
A device is paired to the workspace once. That pairing is what lets it sell for your events, and it can be revoked from settings the moment a phone goes missing. Grouping devices by location keeps a multi-room venue or a festival with several gates legible.
No per-seat pricing
There is no charge per member and no charge per device, because charging for the crew would push people towards shared logins. Invite the whole team and pair as many devices as the night needs.
Getting it running
What you actually do, in order, the first time.
- 01
Invite your members
By email, from team settings. They join with their own account.
- 02
Set what each one can reach
Grant only the areas their job needs. You can change it later without recreating anything.
- 03
Add the door crew
Create personnel with PINs, and decide whether they sell, scan, or both.
- 04
Pair the devices
Once per phone or tablet, grouped by location if you have more than one gate.
At a glance
| Members | Invited by email; each joins with their own account |
|---|---|
| Permission areas | Events, tickets, orders, customers, analytics, settings, billing, members, POS |
| Granularity | Read, manage, publish, scan and more, depending on the area |
| Door crew | POS personnel with PINs, separate from workspace accounts |
| Devices | Paired per device, revocable at any time |
| Sessions | Recorded per person, so a shift can be traced |
| Locations | POS devices can be grouped by location |
| Cost | No per-seat charge. Invite the crew you need |
Questions, answered
How many people can I invite?
As many as you need. There is no per-seat charge, because pricing that punishes you for adding your team just produces shared logins.
Can someone build an event without being able to publish it?
Yes. Creating, editing and publishing are separate permissions, so a producer can prepare an event and an owner can decide when it goes on sale.
Do door staff need a Verimly account?
No. They sign in to a paired device with a PIN. Workspace accounts are for the people who run the business, not for one night on the door.
What happens if a POS device is lost?
Unpair it from workspace settings. That device can no longer sell or scan, and nobody else has to change a password.
Can I see who did what?
POS sessions are recorded per person, and orders carry their own event history, so a question about a particular sale has an answer.
Can I give someone access to the numbers only?
Yes. Analytics is a separate permission from orders, customers, settings and billing.
Keep reading
- Door sales and QR check-inYour door crew needs a phone, not rented hardware and a separate contract.
- Live sales and the storefront funnelOn-sale day, you want to know whether it is working right now, not tomorrow morning.
- Orders, refunds and customer recordsMost of the work happens after the sale, and it is the part most tools leave to a spreadsheet.
See it for a specific kind of event
Get started
Free to set up. You pay when a ticket sells.
No subscription, no setup fee, nothing to cancel. Build the whole thing, and decide at the end whether to publish it.