Skip to main content
These are the fields for members, departments, crew fields, dress presets, reminders, onboarding, availability requests, forms and knowledge sections. How to read a row, the fields at the top of the file and the other records are in Import file fields. Every field here is Stable for version 2.x.

Team members (members[])

People to add to the organization’s team, with their roles and positions.

Example: team members

A team member with a role and two positions.

Departments (departments[])

The organization’s departments (sound, lighting, video) and who is in each one. Imported only when departments are turned on for the organization. Give a record a ref (any short name, such as main-stage) so other records in the same file can point at it. A department matches the org’s department with the same name, ignoring case. A matched department keeps its name, short code, color and description; the file only adds people to it. A person is matched to an active member by email; people the file leaves out stay in the department. external_id is kept for reference and does not match a record. Below the Team plan, outside a free trial, a department in the file that the organization doesn’t have yet is left out with a warning; people are still added to departments that already exist.

Example: departments

A department with its lead and one other member, both added in the same file.

Crew fields (crew_fields[])

The crew record fields the organization tracks for each person (licenses, tax forms, emergency contacts). Reference only: import never creates or changes a field; members[].crew_record fills values into fields that already exist. Workspace export writes them for organization admins when crew records are on.

Example: crew fields

Crew fields listed for reference beside the values a member fills into them.

Dress presets (dress_presets[])

The organization’s dress code presets that gigs pick from. Exported for people who manage gigs; imported only for org admins. A preset matches the org preset with the same key, or else the same label ignoring case. A matched preset is left unchanged; the file only adds presets the org does not have.

Example: dress presets

A dress preset with its own wording for each variant.

Standing reminders (standing_reminders[])

Reminders the organization shows crew on every gig, one per row. Import adds the lines the org does not have yet and never removes one.

Example: standing reminders

Reminders the crew sees on every gig.

Onboarding flow (onboarding_flows[])

The steps a new member completes for the organization. Workspace export writes it for organization admins on a plan with custom onboarding. Import creates it, turned off, only when the organization has no flow yet; an existing flow is never changed. Member progress and submissions stay out.

Example: onboarding flow

An onboarding flow whose document step names a file already in the organization.

Availability requests (availability_requests[])

Availability checks the organization sent, with their days and each recipient’s answers. Reference only; import ignores them. Each person’s own availability entries and the notes they wrote stay out.

Example: availability requests

An availability request with one answer, listed for reference.

Forms (forms[])

The organization’s forms (questionnaires, feedback and general forms) with their current questions. Workspace export writes them for people who manage clients and forms. Import creates a form only when the organization has no form with the same title, checked the same way as a form saved in the app; an existing form is never changed. Agreement templates, form files, requests, answers and signatures stay out.

Example: forms

A published questionnaire with one choice question and a note.

Knowledge sections (knowledge_sections[])

Knowledge base sections the team wrote for the organization (overview, services, venues and the rest). Workspace export writes them for people who manage gigs. Import, for organization admins, adds a section the organization does not have and replaces one the knowledge base generated; a section the team already wrote is never changed. Generated sections stay out.

Example: knowledge sections

Two knowledge sections the team wrote.