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

# Positions

> Define the org-scoped roles members fill for your gigs — and keep names consistent across onboarding, call lists, staffing, and imports.

A **position** is a functional role your organization staffs for — Lead Vocals, FOH Engineer, Tour Manager. Positions are defined once, at the organization level, and reused everywhere: onboarding, call lists, gig team-building, and crew availability.

***

## Positions vs roles

Positions describe the *work* someone does. [Roles](/organization/roles-permissions) describe their *access*. They're independent.

| Concept      | Controls                                                      |
| ------------ | ------------------------------------------------------------- |
| **Role**     | Access level — Owner, Admin, Gig Coordinator, or Member       |
| **Position** | A member's functional skill or crew role — Drums, Sound, etc. |

For example, someone can be a **Member** with positions for **Guitar** and **Vocals**, while a **Gig Coordinator** schedules gigs without any performance position at all.

***

## Why define positions

* **Consistency** — standardized role names across every gig and report
* **Speed** — pick from a list instead of retyping roles each time
* **Matching** — members carry positions, so Soundcheck can suggest the right people when you staff a gig
* **Coverage** — see who can fill each role and spot gaps

***

## Managing the catalog

<Steps>
  <Step title="Open Positions">
    Sidebar → **Organization** → **Positions**.
  </Step>

  <Step title="Add a position">
    Choose **Add position**, enter a name, optionally a description, and save.
  </Step>

  <Step title="Edit or remove">
    Edit renames it everywhere it's referenced; delete removes it from the catalog.
  </Step>
</Steps>

| Field           | Required | Description                         |
| --------------- | -------- | ----------------------------------- |
| **Name**        | Yes      | The role title (e.g. "Lead Guitar") |
| **Description** | No       | Extra detail about the role         |

<Note>
  Renaming a position updates it across past and future references — keep names professional, since they can appear on invoices and contracts.
</Note>

<Warning>
  Deleting a position removes it from historical assignments. If you may need it for records, keep it rather than deleting.
</Warning>

***

## Positions and imports

When you [import](/features/imports/overview) events or members, Soundcheck matches each position name (case-insensitively) against your catalog.

* **Match found** → the member is linked to the existing position.
* **No match, auto-create on** → the position is **created automatically** and added to your catalog, then linked. Subsequent rows with the same name reuse it.
* **No match, auto-create off** → the row is skipped with a warning: *"unknown position — skipped (add it to the org catalog or enable auto-create)."*

<Note>
  The placeholder name `default` (common in exports from other tools) is treated as a non-position and skipped — it never creates a catalog entry.
</Note>

<Tip>
  If you'd rather control your catalog tightly, seed your positions first and leave auto-create off — unknown names then surface as warnings you can review instead of silently expanding the list.
</Tip>

***

## Member positions

Members carry the positions they can fill. These are set two ways:

* **By the member** during onboarding (the Positions step) or on their profile.
* **By an owner or admin** directly from the member's profile.

<Warning>
  Saving a member's positions **replaces** their previous set rather than adding to it — review the full selection before saving.
</Warning>

Assigned positions feed crew calendars, availability requests, call lists, onboarding, and gig team-building.

### Positions during onboarding

Add a **Positions** onboarding step so members pick the roles they play from your active catalog. The step assigns from the existing catalog only — create or update your positions first so the choices are right.

<Card title="Organization setup" icon="building" href="/organization/setup#positions-step">
  Add the Positions step to onboarding.
</Card>

***

## Positions on a gig

When building a gig's team:

<Steps>
  <Step title="Add a position">
    In the gig's team section, add a position from your catalog.
  </Step>

  <Step title="Add multiples as needed">
    The same position can appear several times — 2× Background Vocals, 3× Security.
  </Step>

  <Step title="Set per-position detail">
    Performance fee, fee notes, and any special instructions.
  </Step>
</Steps>

***

## Naming conventions

Consistent names keep reporting and staffing clean:

* Prefer "Lead Vocals" over "singer"; "Sound Engineer — FOH" over "Sound"
* Group with prefixes — "Vocals — Lead", "Vocals — Background", "Guitar — Lead", "Guitar — Rhythm"
* Standardize across the org: "Lead Guitar", never a mix of "Lead Guitarist" and "Guitar 1"

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="A position doesn't show up on a gig">
    Confirm it's saved in the catalog and refresh the gig. Check you have permission to edit the gig.
  </Accordion>

  <Accordion title="An import skipped some positions">
    Those names weren't in your catalog and auto-create was off. Add them to the catalog (or enable auto-create) and re-run the import.
  </Accordion>

  <Accordion title="Can't delete a position">
    It may be in use on active gigs. Consider keeping it rather than deleting to preserve history.
  </Accordion>
</AccordionGroup>

***

## Related guides

<CardGroup cols={2}>
  <Card title="Teams overview" icon="people-group" href="/organization/teams/overview">
    How team management fits together
  </Card>

  <Card title="Call lists" icon="list-check" href="/organization/teams/call-lists">
    Saving rosters with call order
  </Card>

  <Card title="Team building" icon="user-plus" href="/features/gigs/team-building">
    Staffing events
  </Card>

  <Card title="Imports" icon="file-import" href="/features/imports/overview">
    Bulk-load events and members
  </Card>
</CardGroup>