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

# Staffing permissions and privacy

> Who can staff a gig, who sees pay, how a crew chief can run a call without seeing rates, what crew see about each other, and how phone numbers and texts are handled.

Rates are the most sensitive thing in staffing. Owners want coordinators and crew chiefs to run calls without seeing what everyone earns, and crew want their phone numbers kept to the people who need them. This page sets out who can do what, where the limits are, and where they aren't.

![Team settings listing staff with their role, positions and seat usage](https://mintcdn.com/soundchecklive/EpuwxNqbqHAHt986/images/organization/members-light.png?fit=max\&auto=format\&n=EpuwxNqbqHAHt986\&q=85\&s=889370fac59a179e0defe7cafd416714)

Organization roles are covered in full on [Roles and permissions](https://docs.soundchecklive.io/settings/team/roles-permissions.md). Access to one gig is on [Who can see and do what on a gig](https://docs.soundchecklive.io/features/gigs/access.md).

## Who can staff a gig

Staffing a gig means building shifts, sending offers, asking for availability and changing who is on it.

| Who | Where they can staff |
| - | - |
| **Owner**, **Admin** | Every gig |
| **Gig Coordinator** | Every gig (early access, see below) |
| A member with **Staffing on every gig** (extra access) | Every gig |
| A member assigned **Staffing** or **Lead** on a gig | That gig only |

**Finance** and plain **Member** can't staff.

The **Crew** page (crew calendar, schedule, needs) shows for Owners, Admins, Finance and Gig Coordinators, and for anyone with a **Staffing** assignment, once your organization uses crew staffing. Inside it:

* **Needs** shows to gig managers and to people with **Staffing** assignments.
* **Teams** shows to Owners, Admins and Finance.
* **Timesheets** shows to people who can view the time clock.

## Who sees pay

| Who | Sees |
| - | - |
| **Owner**, **Admin**, **Finance**, and members with **Organization finances** | Every gig's money: fees, rates, payables, P\&L |
| A member assigned **Finances** or **Lead** on a gig | That gig's money |
| **Gig Coordinator** | Each person's crew pay on every gig, draft and sent, in **Edit shift** and on the crew board when **Show pay** is on. Not members' rates: the crew picker shows **Member rate applies**. No ledger, income, client billing, P\&L, payouts or the gig's own fee. Times on timesheets, not amounts. |
| **Staffing** assignee | The board without pay, and not members' rates. Each person's pay on a sent shift, in **Edit shift**. |
| Crew | Their own pay, and the shift's rate before they accept. Never anyone else's pay. |

On the crew board, pay shows only to people who can see that gig's money, and only while **Show pay** is on in the view menu.

### Who can change pay

* **Crew pay on a gig** (invitation fees and crew offer fees): Owner, Admin, Finance, Gig Coordinator, and the gig's **Finances** or **Lead** assignee. Editing is blocked on archived gigs and on past gigs once they are locked, like other money edits.
* **Rates on unsent crew**: needs finance access ("Financial permission required to edit unsent crew rates").
* **After a shift is sent**, its rates are locked ("Rates can only be changed on draft positions"). See [Pay and rates](https://docs.soundchecklive.io/features/gigs/staffing/pay-and-rates.md).
* **A member's day rate and hourly rate per position**: Owner and Admin, on the member's profile under **Org Positions**.

## Crew chiefs: running the call without seeing rates

This is the question buyers ask most, so here is the straight answer.

**Partly.** A crew chief can build and run shifts on a gig without pay showing on the crew board. **But Soundcheck hides rates on the board, it doesn't lock them away from everyone who staffs.** **Edit shift** is the exception: once a shift is sent, anyone who can staff the gig sees the shift's fee and each person's fee there. On a draft shift, pay stays hidden from them unless they have finance access.

Pick the setup that matches what your crew chief does:

| The crew chief needs to | Give them | Do they see pay in the app? |
| - | - | - |
| Build shifts, send offers, add people and chase replies on one gig | **Staffing** on that gig | Not on the board. **Edit shift** shows each person's pay once the shift is sent. |
| Do that on every gig | **Staffing on every gig** | Not on the board. **Edit shift** shows each person's pay once the shift is sent. |
| Clock crew in and out and fix wrong times, on any gig | The **Gig Coordinator** role | No. They see times, not amounts. |
| Approve hours | **Lead** on that gig | Yes. Approving hours needs sight of that gig's money. |
| Just run the day, without changing anything | Nothing. Send them the **Day sheet** and **Crew list**. | No. The day sheet never includes pay, and the crew list has no pay column. |

**1. Mark them on the shift**

On the crew board, open the person on their shift and set **Lead / contact for the unit**, so the crew know who to report to. This labels them. It doesn't give them access.

**2. Give them what they need**

On the gig, open **Gig staff** and assign **Staffing**. See [Assigning people to run a gig](https://docs.soundchecklive.io/features/gigs/assignees.md).

**3. Approve hours yourself**

Keep approving hours with the Owner, an Admin, Finance, or a **Lead** you trust with money.

What Soundcheck doesn't have today:

* **Department-scoped access.** A department lead can't be limited to their department's staffing. Access is per gig or per organization. The workaround is a **Staffing** assignment per gig.
* **Access limited to a coordinator's own clients or region.** A Gig Coordinator sees every gig.
* **Separate sign-off by the client.** Clients can't approve hours.

## Owner and Admin only

These need the Owner or an Admin:

* Positions, their short codes and default day rates.
* Departments, and the department lead.
* Crew record fields, crew sharing and custom onboarding.
* Dress presets and standing reminders for crew.
* Time clock settings, including overtime.
* Members' day and hourly rates per position.
* Switching your organization from invitations to crew staffing.
* Inviting or removing members and changing roles. Only the Owner makes someone Admin or Finance.

**Sending payouts** and **payment settings** belong to the Owner and Finance only. Admins record payments made outside Soundcheck but don't send money.

### Cancelling or removing crew on a sent shift

Once a shift is sent, only **Owners**, **Admins** and **Gig Coordinators** can cancel it, remove someone from it, or remove someone from a day. A **Staffing** or **Lead** assignee can add people to a sent shift but can't take confirmed crew off it. Removing someone voids their unpaid pay line. A gig that is completed and settled must be reopened first.

The same three roles can record an answer for someone, such as an accept they gave you on the phone.

## The Gig Coordinator role

> [!NOTE]
>
> **Early access.** The Gig Coordinator role is rolling out. If it isn't offered when you invite someone or change a role, contact [info@soundchecklive.io](mailto:info@soundchecklive.io).

A Gig Coordinator is for a booking agent, production manager, labor coordinator or crew scheduler. They:

* Create, edit, publish and staff every gig.
* Manage the crew calendar and availability requests.
* Apply and save teams on a gig.
* See and set each person's crew pay on every gig.
* Clock crew in and out and fix times on the time clock, without seeing hours pay.
* Import data, and invite people as Member.

They don't see the gig's ledger, income, client billing, P\&L, payouts or the gig's own fee, can't send payouts, can't approve hours, and can't manage members or settings. To let one see a single gig's money, assign them **Finances** on that gig. A Gig Coordinator uses a staff seat.

## Extra access for one member

An Owner or Admin can give one member part of every gig without changing their role, from **Manage access…** on the member:

* **Staffing on every gig**
* **Run of show on every gig**
* **Checklist on every gig**
* **Organization finances** (view money everywhere)
* **Customers, venues and leads**

See [Extra access for one member](https://docs.soundchecklive.io/settings/team/roles-permissions.md#extra-access-for-one-member).

## Timesheets: who views, fixes and approves

| | View times | Fix times | Approve |
| - | :-: | :-: | :-: |
| Owner, Admin, Finance | ✓ | ✓ | ✓ |
| Gig Coordinator | ✓ | ✓ | — |
| **Lead** on the gig | ✓ | ✓ | ✓ |
| **Finances** on the gig | ✓ | — | — |

Nobody approves their own hours. Amounts show only to people who can see that gig's money. See [Time clock](https://docs.soundchecklive.io/features/gigs/staffing/time-clock.md).

## What crew see

On a gig they work, crew see the published schedule, their own call, their own pay, their tasks and the venue's access details. A draft gig is hidden from them.

About other crew on the same shift, Soundcheck sends a crew member names and reply status only. It doesn't send them other people's email, company, notes, special instructions or pay.

Clients in the client portal see their own events, contracts, invoices, forms and files, not your crew list. [Collaborators](https://docs.soundchecklive.io/features/gigs/people/collaborators-and-clients.md) see only the items you share and never see money. To give a client a staffing summary without pay, send the **Day sheet** or **Crew list** PDF.

## Phone numbers and texts

* **Texts need consent from people without an account.** Someone you add to a shift without an account gets an email when your organization can email people without an account. They get a text only if you also ticked **Text them at this number** with their consent.
* **Opt-out works.** A crew member who replies STOP, STOPALL, UNSUBSCRIBE, CANCEL, END or QUIT gets no more texts. START, UNSTOP or YES turns them back on. If Soundcheck can't check someone's opt-out status, the text isn't sent.
* **Crew choose their channels.** Each person picks email, text and push for offers, invitations and availability checks. Their choice beats your organization's default. A gig invitation still arrives the way the sender chose, and texts about a gig's date, time or venue changing, or about the gig being deleted, go out whatever anyone's settings say.
* **Reply codes.** Crew can answer an offer by text with "YES \{CODE}" or "NO \{CODE}". A code lasts 30 days.
* **Who sees phone numbers.** Gig managers see crew phone numbers on the crew list and can **Copy phones** on mobile. The roster **Export CSV** with phones and addresses is Owner and Admin only.
* **No quiet hours.** Soundcheck doesn't hold texts overnight today. Send late-night changes by email or wait until morning.

## Crew documents and data

* **Crew records** hold things like W-9 status, licences and certifications, with files. Owners and Admins edit them. Each field is private to your organization unless you mark it **Share with connected orgs**. See [Crew records](https://docs.soundchecklive.io/settings/organization/crew-records.md).
* **Sharing with another company.** Crew sharing shares people and only the fields you mark shared, read only. The other organization's own notes on a person stay with them. Crew personal data isn't shared with other companies otherwise.
* **Deleting an account.** Crew can delete their own account from the app's settings with **Delete Account**.
* **Audit log.** **Settings → Security → Audit log** records who changed what, from where and when. It is an Enterprise feature. See [Audit log](https://docs.soundchecklive.io/settings/organization/admin-logs.md).
* **Single sign-on.** Not a setting today. Contact [info@soundchecklive.io](mailto:info@soundchecklive.io) about your sign-in requirements.

## Worked example: a production company with a crew chief per show

A production company runs four corporate shows a week. The owner handles pay. Each show has a crew chief who staffs the stagehands and runs the floor.

1. The owner assigns the crew chief **Staffing** on their gig. The crew chief builds the stagehand shifts and sends them. Pay doesn't show on their board.
2. The day before, a stagehand taps **Can't make it** and withdraws. The crew chief adds a replacement to the shift and sends it.
3. The owner's office manager is a Gig Coordinator. She clocks in a stagehand whose phone died and fixes a missed clock-out. She sees times, not pay.
4. After the show, the owner approves the hours and exports them for payroll.
5. Because the owner doesn't want any crew chief able to look up rates, the newest chief only gets the day sheet and crew list until she's trusted with staffing.

## Questions this page answers

* Can I hide pay rates from crew chiefs and other crew while they still run the call? ([FAQ](https://docs.soundchecklive.io/features/gigs/staffing/faq.md))
* What can a crew member see about other crew on the same gig?
* Can a client see the crew list without rates or phone numbers?
* Can I give a department head control of only their department?
* Can a partner company staff part of my gig without seeing my other data?
* Who approves timesheets and who can change them?
* Can I see an audit log of who changed a rate, time or booking?
* Where are crew documents stored, and who can open them?
* Can crew delete their account?
* Can I limit a coordinator to their own clients or region?
* Does Soundcheck support single sign-on?
* Is crew personal data shared with other companies?
* Can I control who sees my phone number?

## Related

> [card] [Roles and permissions](https://docs.soundchecklive.io/settings/team/roles-permissions.md)
>
> Every role and capability, generated from the permission registry.

> [card] [Who can see and do what on a gig](https://docs.soundchecklive.io/features/gigs/access.md)
>
> Gig staff, crew, collaborators, clients and guests.

> [card] [Pay and rates](https://docs.soundchecklive.io/features/gigs/staffing/pay-and-rates.md)
>
> How fees are set and when they lock.

> [card] [Crew records](https://docs.soundchecklive.io/settings/organization/crew-records.md)
>
> What you keep on file and what you share.


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