Work with external co-organizers

External co-organizers work on selected events inside your venue’s existing Usetix account. They use the same event editor as your team, while your venue keeps its shop, payment setup and account administration.

For example, a guest promoter can manage Friday’s club night without seeing Saturday’s event or your account-wide customer list. You choose the events each person can access. The External co-organizer role has one fixed set of permissions; there are no individual permission switches to configure.

Invite a co-organizer

As a venue owner or manager:

1. Open the event in the dashboard.
2. Open its ⋯ menu and choose Invite co-organizer.
3. Enter the person’s email address and send the invitation. The role and this event are already selected.

To assign several events, use Settings → Team, choose External co-organizer, and select the allowed events when inviting the person.

The recipient opens the email invitation and signs in with that email address. Invitation links expire after seven days; pending invitations can be resent or revoked from Team. With one assigned event, the co-organizer lands at that event. With several, their event list contains only the assigned events.

A person can use the same login for several events and venue accounts. Inviting an existing active team member does not replace their current role or reduce broader access. To change an existing member’s role, edit their access in Team explicitly.

What can they do?

Within their assigned events, co-organizers can:

• Edit event details, dates, venue, capacity, descriptions, images, galleries, downloads, FAQs and line-up.
• Manage tickets, prices, event promo codes, ticket design and event seating.
• Publish, unpublish, change shop visibility or delete events, subject to the usual validations.
• View event orders, manage participants and guest lists, edit checkout answers and export data.
• Read historical analytics and Live View for their assigned events.

Changes to published event content become visible immediately. Existing completed purchases retain their recorded prices.

The venue keeps account-wide shop settings, payment connections, refunds, team administration, account tokens, advertising and reusable venue/seating templates. Creating events, including copies of existing events, stays with the venue. Co-organizers cannot duplicate events through the dashboard, personal API tokens, the assistant or MCP. Account-wide scanner access is not included in this role.

Ticket revenue continues to go through the venue’s payment setup. The venue and co-organizer arrange their settlement themselves; assigning events does not split payments or change the seller shown at checkout.

Orders and participants

A buyer can purchase tickets for several events in one order. A co-organizer sees only the admissions and answers for the events they can access, together with the buyer and participant details needed for that work.

They do not see other events’ items, whole-order totals, invoices or links to the buyer’s complete order. Editing one event’s answers preserves the other events’ answers.

For example, if an order contains €40 for an assigned event and €30 for another event, the co-organizer’s event revenue includes €40. The venue can see the complete order.

Analytics

Open Analytics to view all currently assigned events together, or select one event. Historical reports, Live View and dashboard CSV exports use the same scope. Combined reports count an order or session spanning several assigned events once; revenue includes only those events’ shares. Shop-wide page views without an event are excluded.

Public report sharing and switching analytics collection on or off remain with the venue. Previously collected data remains available when collection is paused. See the Analytics API reference for integrations.

Personal security

Open Security from the user menu to register, rename or remove your own passkeys and revoke your other active sessions. Passkeys belong to your personal login across venue accounts. Other users’ credentials and sessions are inaccessible. This page remains available even without assigned events.

Personal integrations

API Tokens: Co-organizers create their own tokens from the sidebar. A read token can read permitted data; a write token can also make permitted changes. Both follow the membership’s current event assignments. A write token adds no account-wide rights. Use the co-organizer’s own token for the CLI or an API integration; a shared venue-owner token retains its wider permissions.

AI assistant and MCP: The built-in assistant and connected MCP clients use the same event access. Account-wide tools unavailable to the role remain blocked.

Webhooks: Co-organizers manage their own endpoints under Webhooks. Each endpoint automatically follows all currently assigned events. Order payloads contain only the relevant tickets and answers, without whole-order financial or payment data. Personal endpoints support order, event publication and ticket redemption actions; voucher actions are unavailable. See personal webhook payloads and the Webhook API.

Change or remove access

In Settings → Team, edit the member’s role and event assignments. Remove an event to end access to that event, or deactivate the membership to end access to the venue account.

Updated assignments apply to the next page, API or tool request, including existing integrations and forms already open. Deactivation invalidates personal API tokens. Removing all assignments leaves the person with no accessible events or event analytics.

Personal webhook deliveries are checked again before sending. Unauthorized queued deliveries are discarded; a prepared retry is discarded if any included event is no longer assigned. Files or data already downloaded or delivered cannot be recalled. Access to other venue accounts remains separate.

If the co-organizer sees No events assigned, a venue owner or manager needs to assign an event in Team.