Roles and permissions
TimbaTicket has three standing roles inside an organisation — Owner, Manager, Team — plus per-event door staff. Owners can do everything (including refunds and managing other owners and managers); managers run events day-to-day; team members get limited event access.
The roles
| Role | What they can do |
|---|---|
| Owner | Everything: refunds, managing Owners/Managers, payment/Square config, branding, finances. |
| Manager | Run events day-to-day: create/edit/publish events, ticket types, discount codes, door staff, media, Settings/branding. Sees financial & sales reports, Orders and Analytics. Can invite/remove Team members only. Cannot refund, cannot manage Owners/Managers. |
| Team | Limited event operations — cannot see finance or manage members. |
| door staff | Check-in access to one specific event only (created per event by the organiser). Not a standing seat. |
Owner-only actions
- Refunds.
- Managing Owners and Managers.
- Connecting the organisation's Square account (payment setup).
- Viewing the full combined-finance picture across organisations you belong to (Team/door staff callers are excluded from the combined sums).
Door staff
Door staff are per-event access (scoped to that event's id). They don't count against your plan's team seats and they can't open other events. At the door, the "Admit anyway" override is available to Owners and Managers only.
The Console (staff)
TimbaTicket's own team has a separate staff-only Console for platform administration. It is internal — never part of customer-facing docs.
Was this article helpful?