> ## Documentation Index
> Fetch the complete documentation index at: https://docs.soundchecklive.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Team and organization import fields

> Import file fields (version 2.0) for members, departments, crew fields, dress presets, reminders, onboarding, availability requests, forms and knowledge sections, with an example for each.

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](https://docs.soundchecklive.io/features/imports/import-format-reference.md). 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `members[].email` | email | Yes | Stable | The person's email address — also the claim key when they sign up via Clerk. |
| `members[].role` | string | | Stable | Org role: Member (default), Admin, Finance, or Gig Coordinator. Matching ignores case, a Clerk org: prefix (org:admin is Admin) and runs of spaces, hyphens, underscores and dots. An Owner is invited as Admin when the email is new; an existing member keeps their current role. A misspelt role is corrected to the role it means, with a warning in validation and spreadsheet previews; text that matches no role is refused, never set to Member. One of `Member`, `Admin`, `Finance`, `Gig Coordinator`. |
| `members[].first_name` | string | | Stable | First name. |
| `members[].last_name` | string | | Stable | Last name. |
| `members[].phone_number` | phone | | Stable | Stored on the temp member; carried over to the real User once they claim. |
| `members[].notes` | string | | Stable | Free-form notes about this person — visible to org admins. |
| `members[].status` | string | | Stable | ACTIVE or INACTIVE. INACTIVE keeps a past person for history only: they stay the booked person on past shifts and are never invited, offered work or counted as a seat. Blank leaves an existing member as they are and adds a new one as ACTIVE. Import never deactivates someone who has claimed their account. One of `ACTIVE`, `INACTIVE`. |
| `members[].legal_name` | string | | Stable | Name as it appears on government ID, for booking travel. Stored with the pending member and copied to their profile when they claim it; never overwrites a value already on the profile. |
| `members[].date_of_birth` | `YYYY-MM-DD` | | Stable | For booking travel. Stored with the pending member and copied to their profile when they claim it; never overwrites a value already on the profile. An unreadable date is left blank with a warning. |
| `members[].preferred_airport` | string | | Stable | Home airport for booking travel (code or name, up to 100 characters). Stored with the pending member and copied to their profile when they claim it; never overwrites a value already on the profile. |
| `members[].metadata` | object | | Stable | Optional JSON map for arbitrary custom fields (employee ID, T-shirt size, etc.). Paste as JSON: \{"employee\_id":"E-123"}. |
| `members[].positions[].name` | string | | Stable | Position name. |
| `members[].positions[].rating` | integer 1–5 | | Stable | Position rating. |
| `members[].positions[].notes` | string | | Stable | Position notes. |
| `members[].positions[].day_rate` | decimal | | Stable | Position day rate. |
| `members[].positions[].hourly_rate` | decimal | | Stable | This person's hourly rate for the position. A shift paid by the hour uses it as their fee when the booking states no rate. |
| `members[].positions[].default_day_rate` | decimal | | Stable | Position default day rate. |
| `members[].crew_record[].field` | string | Yes | Stable | The crew field this value fills, by its label (crew\_fields\[].label). Matched to an existing field ignoring case; a field the org does not have is skipped with a warning. |
| `members[].crew_record[].value` | string | Yes | Stable | The person's value, checked against the field's type: YES\_NO takes yes or no, DATE takes YYYY-MM-DD and CHOICE takes one of the field's options. Import fills an empty value and never overwrites one the person already has. Imported for organization admins when crew records are on. |
| `members[].crew_record[].expires_on` | `YYYY-MM-DD` | | Stable | When the value expires, for a field that tracks expiry. Ignored for other fields. |
| `members[].emergency_contacts[].name` | string | Yes | Stable | Who to call in an emergency. Stored with the pending member and copied to their profile's Emergency Contacts when they claim it; never overwrites contacts already on the profile. A contact missing a name, relationship or phone is skipped with a warning, the same rule the profile applies. |
| `members[].emergency_contacts[].relationship` | string | Yes | Stable | Emergency contact relationship. |
| `members[].emergency_contacts[].phone_number` | phone | Yes | Stable | Emergency contact phone. |
| `members[].emergency_contacts[].email` | email | | Stable | Emergency contact email. |
| `members[].home_base.address` | string | | Stable | Where the person is based, for travel and local-hire decisions. Stored with the pending member and copied to their profile's home base when they claim it; never overwrites a home base already on the profile. |
| `members[].home_base.city` | string | | Stable | Home city. |
| `members[].home_base.state` | string | | Stable | Home state. |
| `members[].home_base.postal_code` | string | | Stable | Home postal code. |
| `members[].home_base.country` | string | | Stable | Home country. |

### Example: team members

A team member with a role and two positions.

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "team-roster"
  },
  "members": [
    {
      "email": "dana@example.com",
      "first_name": "Dana",
      "last_name": "Reyes",
      "role": "Gig Coordinator",
      "phone_number": "+15125550101",
      "positions": [
        {
          "name": "FOH Engineer",
          "rating": 5,
          "day_rate": 450
        },
        {
          "name": "Monitor Engineer",
          "rating": 4
        }
      ]
    }
  ],
  "member_options": {
    "auto_create_positions": true
  }
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `departments[].ref` | string | | Stable | Name for this department inside the document. A workspace export writes the record's ID here, so importing that export back into the same workspace matches each department to its own record before it looks at names. |
| `departments[].external_id` | string | | Stable | The department's ID in the source system, kept for reference. |
| `departments[].name` | string | Yes | Stable | Department name. |
| `departments[].short_code` | string | | Stable | Up to 5 characters, shown on the department pill. Stored in upper case. |
| `departments[].color` | string | | Stable | One of the department swatch colors, as a hex value. |
| `departments[].description` | string | | Stable | Department description. |
| `departments[].members[].email` | email | Yes | Stable | An active member of the organization, or a person this file adds in members\[]. |
| `departments[].members[].lead` | boolean | | Stable | True for the department's lead. A department has at most one; a department that already has a lead keeps it. |

### Example: departments

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

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "departments"
  },
  "members": [
    {
      "email": "sam@example.com",
      "first_name": "Sam"
    },
    {
      "email": "alex@example.com",
      "first_name": "Alex"
    }
  ],
  "departments": [
    {
      "name": "Audio",
      "short_code": "AUD",
      "members": [
        {
          "email": "sam@example.com",
          "lead": true
        },
        {
          "email": "alex@example.com"
        }
      ]
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `crew_fields[].ref` | string | | Stable | Name for this field inside the document. A workspace export writes the record's ID here. Reference only; import ignores it. |
| `crew_fields[].label` | string | Yes | Stable | Reference only; import ignores it. |
| `crew_fields[].type` | string | | Stable | One of \{options}. Reference only; import ignores it. One of `TEXT`, `LONG_TEXT`, `NUMBER`, `DATE`, `YES_NO`, `CHOICE`. |
| `crew_fields[].options` | list of strings | | Stable | The choices of a CHOICE field. Reference only; import ignores it. |
| `crew_fields[].help_text` | string | | Stable | Reference only; import ignores it. |
| `crew_fields[].required` | boolean | | Stable | Reference only; import ignores it. |
| `crew_fields[].tracks_expiry` | boolean | | Stable | Reference only; import ignores it. |

### Example: crew fields

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

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "crew records"
  },
  "members": [
    {
      "email": "sam@example.com",
      "crew_record": [
        {
          "field": "Driver license",
          "value": "D1234567",
          "expires_on": "2027-01-31"
        }
      ]
    }
  ],
  "crew_fields": [
    {
      "label": "Driver license",
      "type": "TEXT",
      "tracks_expiry": true
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `dress_presets[].key` | string | | Stable | Lower-case letters, digits and underscores, starting with a letter. Made from the label when left out. |
| `dress_presets[].label` | string | Yes | Stable | Dress preset label. |
| `dress_presets[].men` | string | | Stable | Dress preset for men. |
| `dress_presets[].women` | string | | Stable | Dress preset for women. |
| `dress_presets[].any` | string | | Stable | Dress preset for anyone. |

### Example: dress presets

A dress preset with its own wording for each variant.

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "dress presets"
  },
  "dress_presets": [
    {
      "label": "Cocktail",
      "women": "Black dress",
      "men": "Dark suit"
    },
    {
      "label": "Blacks",
      "any": "All black, closed-toe shoes"
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `standing_reminders[].text` | string | Yes | Stable | Standing reminder. |

### Example: standing reminders

Reminders the crew sees on every gig.

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "standing reminders"
  },
  "standing_reminders": [
    {
      "text": "Bring earplugs"
    },
    {
      "text": "Park in lot B"
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `onboarding_flows[].name` | string | Yes | Stable | Onboarding flow name. |
| `onboarding_flows[].steps[].title` | string | Yes | Stable | Onboarding step title. |
| `onboarding_flows[].steps[].type` | string | Yes | Stable | One of \{options}. One of `FORM`, `DOCUMENT`, `FILE_UPLOAD`, `POSITIONS`. |
| `onboarding_flows[].steps[].description` | string | | Stable | Onboarding step description. |
| `onboarding_flows[].steps[].required` | boolean | | Stable | Defaults to true. |
| `onboarding_flows[].steps[].config` | object | | Stable | The step's settings, such as a FORM step's questions. Checked the same way as a flow saved in the app. |
| `onboarding_flows[].steps[].documents` | list of strings | | Stable | File names of the organization documents a DOCUMENT step asks the member to read, matched to the org's document library by name. A DOCUMENT step whose documents are not all in the library is left out, with a note. |

### Example: onboarding flow

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

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "onboarding"
  },
  "onboarding_flows": [
    {
      "name": "Crew onboarding",
      "steps": [
        {
          "title": "Pick your positions",
          "type": "POSITIONS"
        },
        {
          "title": "Read the handbook",
          "type": "DOCUMENT",
          "required": true,
          "documents": [
            "handbook.pdf"
          ]
        }
      ]
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `availability_requests[].title` | string | Yes | Stable | Reference only; import ignores it. |
| `availability_requests[].description` | string | | Stable | Reference only; import ignores it. |
| `availability_requests[].event_ref` | ref → `events[].ref` | | Stable | The gig the request was for, by events\[].ref. Reference only; import ignores it. |
| `availability_requests[].request_mode` | string | | Stable | One of \{options}. Reference only; import ignores it. One of `TIME_WINDOW`, `DAY`. |
| `availability_requests[].status` | string | | Stable | One of \{options}. Reference only; import ignores it. One of `DRAFT`, `OPEN`, `CLOSED`, `EXPIRED`, `CANCELLED`. |
| `availability_requests[].date` | `YYYY-MM-DD` | | Stable | Reference only; import ignores it. |
| `availability_requests[].start_time` | date-time | | Stable | Reference only; import ignores it. |
| `availability_requests[].end_time` | date-time | | Stable | Reference only; import ignores it. |
| `availability_requests[].expires_at` | date-time | | Stable | Reference only; import ignores it. |
| `availability_requests[].days[].date` | `YYYY-MM-DD` | | Stable | Reference only; import ignores it. |
| `availability_requests[].days[].start_time` | date-time | | Stable | Reference only; import ignores it. |
| `availability_requests[].days[].end_time` | date-time | | Stable | Reference only; import ignores it. |
| `availability_requests[].recipients[].email` | email | | Stable | Reference only; import ignores it. |
| `availability_requests[].recipients[].status` | string | | Stable | One of \{options}. Reference only; import ignores it. One of `PENDING`, `AVAILABLE`, `UNAVAILABLE`, `EXPIRED`, `WITHDRAWN`. |
| `availability_requests[].recipients[].days[].date` | `YYYY-MM-DD` | | Stable | Reference only; import ignores it. |
| `availability_requests[].recipients[].days[].status` | string | | Stable | One of \{options}. Reference only; import ignores it. One of `PENDING`, `AVAILABLE`, `UNAVAILABLE`, `EXPIRED`, `WITHDRAWN`. |

### Example: availability requests

An availability request with one answer, listed for reference.

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "availability"
  },
  "availability_requests": [
    {
      "title": "December holds",
      "request_mode": "DAY",
      "status": "OPEN",
      "days": [
        {
          "date": "2026-12-12"
        }
      ],
      "recipients": [
        {
          "email": "sam@example.com",
          "status": "AVAILABLE",
          "days": [
            {
              "date": "2026-12-12",
              "status": "AVAILABLE"
            }
          ]
        }
      ]
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `forms[].ref` | string | | Stable | Name for this form inside the document. A workspace export writes the record's ID here. Reference only; import ignores it. |
| `forms[].title` | string | Yes | Stable | Matched to the organization's forms and agreement templates by title, ignoring case and extra spaces. A form whose title is taken is left unchanged. |
| `forms[].purpose` | string | | Stable | One of \{options}. Defaults to GENERAL. One of `EVENT_QUESTIONNAIRE`, `GENERAL`, `FEEDBACK`. |
| `forms[].published` | boolean | | Stable | True to publish the form when it is created, so it can be sent. A form that is not published is created as a draft. |
| `forms[].items[].kind` | string | Yes | Stable | One of \{options}. File items stay out of the export, and a new form cannot hold one. One of `question`, `text`. |
| `forms[].items[].id` | string | | Stable | Ties a required\_when condition to a question in the same form. A new form gets fresh ids, and its conditions follow them. |
| `forms[].items[].label` | string | | Stable | The question text. |
| `forms[].items[].type` | string | | Stable | One of \{options}. One of `short_text`, `long_text`, `email`, `phone`, `number`, `date`, `multiple_choice`, `checkboxes`, `dropdown`, `song_list`, `signature`. |
| `forms[].items[].required` | boolean | | Stable | Form question required. |
| `forms[].items[].placeholder` | string | | Stable | Form question placeholder. |
| `forms[].items[].options[].id` | string | | Stable | Ties a required\_when condition to a choice. A new form gets fresh ids. |
| `forms[].items[].options[].text` | string | Yes | Stable | Form choice. |
| `forms[].items[].required_when` | object | | Stable | The condition that makes the question required, checked the same way as a form saved in the app. |
| `forms[].items[].party` | string | | Stable | Who signs a signature question: one of \{options}. One of `recipient`, `company`. |
| `forms[].items[].song_source` | object | | Stable | Where a song list question takes its songs from. A source that names acts or songs the organization does not have leaves the form out. |
| `forms[].items[].markdown` | string | | Stable | The text of a text item. |

### Example: forms

A published questionnaire with one choice question and a note.

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "forms"
  },
  "forms": [
    {
      "title": "Wedding questionnaire",
      "purpose": "EVENT_QUESTIONNAIRE",
      "published": true,
      "items": [
        {
          "kind": "text",
          "markdown": "Tell us about your day."
        },
        {
          "kind": "question",
          "label": "First dance song",
          "type": "short_text",
          "required": true
        },
        {
          "kind": "question",
          "label": "Ceremony style",
          "type": "dropdown",
          "options": [
            {
              "text": "Indoor"
            },
            {
              "text": "Outdoor"
            }
          ]
        }
      ]
    }
  ]
}
```

***

## 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.

| Field | Type | Required | Status | Notes |
| - | - | - | - | - |
| `knowledge_sections[].key` | string | Yes | Stable | One of \{options}. One of `overview`, `services`, `service_area`, `clients`, `venues`, `staffing`, `operations`, `money_rules`, `incidents`, `voice`, `playbook`, `glossary`. |
| `knowledge_sections[].markdown` | string | Yes | Stable | The section as the team wrote it, in Markdown, at most 20,000 characters. |

### Example: knowledge sections

Two knowledge sections the team wrote.

```json theme={null}
{
  "schema_version": "2.0",
  "source": {
    "type": "PASTE",
    "name": "knowledge"
  },
  "knowledge_sections": [
    {
      "key": "overview",
      "markdown": "We play weddings and corporate events across Texas."
    },
    {
      "key": "venues",
      "markdown": "The Grand Hall loads in through the north dock."
    }
  ]
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.