Skip to main content
Staffing a gig answers who is working the show. Assigning answers a different question: who is running it. A gig assignee is an org member you put in charge of some part of a show — staffing it, working its task list, building its run of show, or handling its money — whether or not they are on the crew that day. Assignments show up as avatars on every gig list, and both the web and mobile gig lists gain an Assigned to filter so you can see just the shows you own.
Assignments are about management, not the lineup. The people playing or working the show are its team. The two lists are independent: an assignee is usually not on the crew, and a crew member is usually not an assignee.

​
The five roles

You assign one or more roles per person per gig. Each role grants exactly one slice of that one gig. Lead implies all the others. Assigning someone Lead gives them Staffing, Tasks, Run of show and Finances too, so you don’t need to tick every box.

​
Assignments only ever add

Nobody loses anything when this feature is used.
  • Organization Owners, Admins and Gig Coordinators keep the access they already have on every gig, assigned or not.
  • A plain Member with an assignment gains those rights on that one gig and nothing else. Every other gig in the org looks exactly as it did before.
  • Removing an assignment removes the granted rights, and the gig drops out of that person’s list again.
One consequence worth knowing: because Finances is a real grant, a Member assigned Finances can see that gig’s money, while a Gig Coordinator who is not assigned still cannot — Gig Coordinators have never had financial access, and that has not changed.
Moving money stays with Owners and Admins. Finances grants viewing and editing a gig’s figures. Paying someone, running a batch payout, and reversing a payment remain restricted to organization Owners and Admins, no matter who is assigned. The organization-wide ledger is likewise unchanged.

​
Assigning someone

On a gig’s detail page, use the Assigned control in the header. Search your roster, pick a person, then toggle the roles they should hold. Picking Lead selects the rest for you. Anyone who can manage gigs in the organization can assign people, and so can a Lead on that gig — which is the point of Lead: hand a show to someone and let them build their own crew of managers around it. Assignees get a push notification when they are assigned, and the gig appears in their gigs list right away. You never get a notification for assigning yourself, and re-saving an unchanged set of roles sends nothing.

​
Finding gigs by assignee

Both gig lists have an Assigned to filter:
  • Me — the shows you personally own
  • Unassigned — shows nobody has been put in charge of yet, which is usually the list worth clearing
  • Any person on your roster
The filter narrows the card, table and calendar views together, and combines with the existing type and date filters.

​
What assignments do not do

  • They are not copied. Duplicating a gig, or saving one as a template, leaves the copy unassigned. Who runs a show is a fresh decision each time, not a property of the show’s shape.
  • Templates cannot have assignees at all. A template is a blueprint, not a date on the calendar.
  • They are not an invitation. Assigning someone does not add them to the crew, does not create a shift, and does not affect anyone’s pay.
  • They do not replace org roles. If you want somebody to manage every gig in the organization, give them the Gig Coordinator role in settings instead of assigning them to each show.

​
For agents

The MCP server exposes assignments as list_event_assignees, set_event_assignee and remove_event_assignee. set_event_assignee replaces the whole role set for a person, so pass every role they should end up holding, not just the new one. See the MCP server reference.