# Teams & Client Spaces

Source: https://docs.skaz.io/guide/teams

> Work with others in Skaz: invite editors and viewers to your stories, and file stories into client spaces.

Two ways to keep a bigger body of work in order: **client spaces** to file
stories by who they're for, and **seats** to let other people work on them with
you.

## Client spaces

A client space is a named folder for stories — usually one per client. Available
on **Studio** (5 spaces) and **Team** (unlimited).

**Creating one.** On the Studio dashboard, click **+ Client space** above your
stories, type the client's name and press **Add**.

**Filing a story.** Open the story's page from the dashboard. Under the buttons
at the top there's a **Client space** picker — choose a space, or **No client
space** to take the story out again.

**Filtering.** The chips above your stories switch the dashboard between
**All**, one client, or **Unfiled** — stories not in any space.

**Deleting a space.** Select its chip and click the **×** next to it. The
stories inside aren't touched; they just become unfiled.

> If you move to a plan with fewer spaces, the ones you have stay and keep working —
> you just can't create new ones past the limit. Deleting a space and unfiling
> stories always works, whatever your plan.

## Seats and roles

On **Team**, other people can work on your stories. Open **Team** on the Studio
dashboard, enter a colleague's email, pick a role and click **Invite**:

| Role | Can do |
|---|---|
| **Editor** | Everything with your stories: edit, publish, set domains and webhooks, see statistics, export. |
| **Viewer** | Look, not touch: statistics, sessions, and every export. No editing. |

Only you — the owner — can invite or remove people. Invite someone who's already
on the team again to change their role.

### How they get in

There's no invitation email yet. Tell your colleague to sign in to Skaz with
**the address you invited**. As soon as that address is verified, your stories
appear on their dashboard with a **Team · editor** or **Team · viewer** badge.

> Access requires a **verified** email. Someone who signs up with the address but
> never confirms it gets nothing — otherwise anyone could claim a seat by typing
> your colleague's email into a sign-up form.

### Your plan, not theirs

When a teammate works on your story, **your plan** decides what's possible. A
colleague on a Free account can still export SCORM from your Team story. Their
own stories stay on their own plan.

Stories shared with you don't count against your own
[story limit](/plans#story-limits).

### Leaving and removing

- **Remove** next to a member takes their seat back at once.
- **Leave** under *Teams you're on* gives up your own seat on someone else's
  team.

> If the owner moves off Team, seats are **suspended**, not deleted — the team
> loses access, and gets it back exactly as it was if the owner upgrades again.

> Per-seat billing isn't connected yet. The Team price is per seat, but for now the
> number of seats isn't limited by what you pay.