Crews

A crew is a team that manages several pages from one place. One subscription covers them all, one member list decides who is in, and one set of roles decides what each of those people can touch. An agency running twelve artists, a label with its promoters, a booking office with a shared roster: all of them are one crew holding several pages, rather than a dozen separate logins.

Crews are the only part of the admin where you manage people rather than content, so this page spends most of its length on Members, Roles and Pages.

Open a crew

1. Open Manage.
2. Click the Crews tab.
3. Click the crew you want.

Each card carries the crew name, a tier badge, the slug, how many page slots the plan includes, and either Owner or Member depending on which you are. Manage → takes you in. If you belong to no crew the tab reads No crews yet, with You don't belong to any crew yet. underneath.

There is no button anywhere in the admin that creates a crew. A crew is brought into existence by the Studio subscription itself and appears in this tab once the payment clears. A crew whose subscription later lapses drops back to Basic and keeps everything it had, but stops being able to grow.

What the left rail holds

Two gates decide what you can do

Every crew screen is behind two independent checks, and both have to pass.

Your crew role. A crew works differently from a page. On a page, permissions are granted per person per page, as described in Manage permissions. In a crew you hold exactly one role, and that role covers the whole crew. Its list of features is what the rail reads.

• The crew owner always holds every crew feature. There is no way to reduce the owner, and nothing in a role can grant more than the owner already has. That is what the rail reads. One screen, Presskits, checks the owner's role instead of their ownership and turns them away regardless.
• Everyone else holds precisely what their one role lists. Nothing is inherited, and nothing is implied by seniority.
• A member carrying no role at all holds nothing. The interface always asks for a role when you add someone, so this is unusual, but the data allows it and a few screens handle it less gracefully than others.

The crew plan. Crew plans are Basic, Studio and Roster. The tier gate accepts Studio or Roster and refuses Basic. There is no Starter tier for a crew, so the entry level is Studio. One row sits behind that gate, API, and it carries a permission of its own on top of it. Holding the plan without the permission, or the permission without the plan, leaves the row greyed either way. API opens once both hold.

Greyed out, never hidden

A row you cannot use stays visible and stays greyed, so you always see the shape of what a crew can do even on the rows you personally cannot open. Which grey it is, the hover tells you.

A row you are missing the plan for gets a sparkle at its right edge and the tooltip Upgrade to Starter to unlock this feature. That string is the one the whole admin uses, and it names Starter even here, where no such crew plan exists. On a crew, read it as Studio. The sparkle only draws while the rail is wide.

A row you are missing a permission for gets no sparkle and no explanation. Hovering it on the narrow rail repeats the row's own name back at you, and on the wide rail produces no tooltip at all. That silence is the signal: ask the crew owner, not the billing screen.

Neither of those is the Upgrade button in the top right of the crew Dashboard and Settings screens. That button is a shortcut to Subscription and nothing more, and its own tooltip reads Upgrade your plan to unlock premium features.

Greying is navigation, not a lock. Members and Roles in particular carry no in-page block: reaching either by typing the address shows the whole screen, buttons included, and the refusal only arrives when you try to save. When it does, the message is raw database text rather than a sentence written for you. Read any unexplained failure on those two screens as a missing crew feature.

Dashboard

The crew's landing page, with Manage your crew's team, roles, and pages underneath the name. It writes nothing.

Four figures across the top: Members, Roles, Pages (shown as used out of the plan's total) and Tier. Below them, three shortcuts, Manage Members, Manage Roles and Manage Pages, then a Crew Info card with the Slug and the Created date.

On a Basic crew an Upgrade button appears at the top right and points at the Subscription screen.

If the crew record cannot be read, the whole page becomes Access Denied with You don't have permission to access this page. That is the only access check this screen performs.

The suspended banner

When the subscription is not paying, a warning band appears above the figures: This crew is suspended, with Your pages, members and shares are preserved. Reactivate to attach pages, invite, share, and manage members.

The wording is the important part. Nothing is deleted by a suspension. What stops is growth: attaching pages, sending invitations, sharing, and managing members all refuse with This crew is suspended. Reactivate it to continue. The single button reads Reactivate crew, or Resume subscription when the plan is paused rather than lapsed.

Settings

Heading Crew Settings, subtitle Manage your crew's identity. The tab bar holds Settings, plus Danger Zone for the owner only.

The main tab is two cards. Crew Info holds Crew Name and Slug, with the hint Lowercase letters, numbers, and hyphens only (min 3 chars) under the second. Subscription is read-only: the tier as a pill, and the Created date.

Only the owner can edit here. A member holding the settings feature can open the screen and read it, but both fields are greyed and no Save button is drawn at all. There is a separate "edit settings" feature in the permission picker; this screen does not consult it, so granting it changes nothing on its own.

Rename a crew or change its slug

1. Open Settings.
2. Edit Crew Name, up to 100 characters.
3. Edit Slug. Lower-case letters, digits and hyphens only, up to 50 characters.
4. Click Save. A Crew settings saved confirmation appears.

Delete a crew

1. Open Settings, then the Danger Zone tab.
2. Read Delete this Crew. The warning states that deletion is permanent, that All pages will be detached and that any associated Stripe subscription will be cancelled.
3. Click Delete Crew.
4. Type the crew's exact name into the confirmation box. The button stays disabled until it matches.
5. Click Delete.

Subscription

The rail calls this row Subscription; the page itself is headed Subscription & Billing, with Manage your crew's subscription, billing cycle and add-ons. Everything on it is behind the crew billing feature, which the owner always holds.

On a Basic crew

Two cards: Current Plan showing Basic, and a subscribe card headed No active subscription with Subscribe to Studio to unlock Crew features. A cycle picker offers Monthly — €59/mo or Annual — €590/yr · 2 months free, and Subscribe to Studio starts the checkout. Those two cycle labels are written into the screen in English and stay in English whatever language the rest of your admin is in.

If the crew is on Basic and you do not hold the billing feature, neither block is drawn and no explanation replaces them. The page renders the header and the two small stat cards at the bottom and nothing else. That is the screen working as built, not a loading failure.

On Studio or Roster

The plan card names the tier and lists six lines covering pages, members per page, storage, email, push notifications and support. Read your own allowances there rather than from a table elsewhere, since they move with the plan. A Storage usage bar sits under the list.

A billing card follows with Billing Status, Billing Cycle, Current Period and Extra Pages. The action card underneath holds, depending on state:

• Switch to Annual or Switch to Monthly.
• The extra-pages picker, described below.
• Pause, preceded by a box for the number of days and carrying your remaining yearly allowance in its own label, and Resume once paused.
• Cancel Subscription, or Undo Cancellation if a cancellation is already scheduled.
• Manage Billing, which opens the Stripe portal for invoices and payment methods.

A Roster crew hides that whole action card and shows This subscription is managed by your account manager. instead, with a contact line naming the manager. A failed payment raises Payment Past Due at the top of the page.

Every successful action here reloads the page. A failed cycle switch or extra-page change reports itself in a plain browser alert box rather than in the usual notification corner, so it is easy to miss if you clicked away.

Buy or drop an extra page slot

Studio includes five page slots and sells three more at €12 a month each, to a ceiling of eight.

1. Open Subscription.
2. In the picker, choose 5 pages, 6 pages, 7 pages or 8 pages (max). The price for each step is printed on the option.
3. Click Buy to add slots, or Remove to drop them.
4. Confirm in the dialog.

Options you cannot reach are disabled: you cannot shrink to a size smaller than the pages already attached. When that is the case the screen says so with Your crew uses {used}/{max} page slots. Remove pages from the crew management first before reducing extra pages.

Members

Heading Members, subtitle Manage who is part of your crew and their roles. The table columns are Member, Role, Features, Joined and Actions, with the feature cell showing a count rather than a list. A search box filters the loaded rows by username or role, and the count beside it reads the crew total.

The owner's row has no menu. It shows a padlock and the word Owner, and there is no path from this screen to removing or demoting them.

Add a member

1. Click + Add Member.
2. Type into Search User. Nothing happens under two characters; from there the list of matching usernames appears after a short pause. People already in the crew are filtered out.
3. Click the person you want. A tick confirms the choice.
4. Pick a Role. The list shows every crew role except the owner role, each with its feature count in brackets.
5. Click Add Member. Member added confirms it.

You are searching every Sway account by username, not an address book of your own contacts, so you need the exact username from the person you are adding.

Change a role, or remove someone

The three-dots menu on each row holds two entries.

• Change Role opens a picker of the same non-owner roles. Saving reports Member role updated, and the new role's features apply everywhere at once.
• Remove asks Are you sure you want to remove {name} from this crew? before confirming with Member removed.

Removing someone takes them out of the crew and out of everything the crew gave them. It does not touch permissions they hold on a page in their own right, which were granted on that page and live on after they leave.

Roles

Heading Roles, subtitle Define roles with specific feature access for your crew. Roles are listed one per row, Discord style: the name, a summary naming the first three feature areas it touches followed by a +N for the rest, and two pills counting the members holding it and the features in it.

Roles shipped with the crew carry a padlock and a System badge. Their features can be edited but their names cannot, and they have no Delete entry. Opening one shows System role "{name}" cannot be renamed, but you can edit its features.

The owner role is stricter still: its only menu entry is View, which opens the feature list read-only.

Create a role

1. Click Create Role.
2. Type a Role Name, up to 50 characters.
3. Optionally pick Start from template. The first option is Blank (no features); the rest are the shipped role shapes with their feature counts. Choosing one pre-ticks its features, which you can then edit freely.
4. Work through the feature picker. It groups features by area, has its own search box and a Select all per group, and marks the dangerous ones with Sensitive permission — destructive or billing-level access.
5. Click Create Role.

Duplicate, edit and delete

Duplicate copies a role instantly, with no dialog and no confirmation. The copy takes the original's name with (copy) on the end and appears in the list straight away. It is the fastest way to build a slightly narrower version of a role you already trust.

Edit reopens the name and the feature picker. Delete opens a typed confirmation that first counts who holds the role:

• Members hold it: member(s) currently have this role. They will need to be reassigned before deletion is possible.
• Nobody holds it: No members are currently assigned this role. Safe to delete.

Either way the Delete button stays disabled until you type the role's exact label into the box.

Pages

The largest crew screen, and the one worth reading twice. Heading Pages, subtitle Attach pages to your crew and assign members to them.

Four tabs, Artists, Venues, Promoters and Events, each badged with its count.

The quota

The header reads / {max} pages used. Two things about that figure surprise people:

• Events never count. An event reaches the crew through its promoter, so event pages are inherited rather than attached. They appear in the Events tab with an Inherited from {promoter} pill, they cannot be expanded, they cannot be removed here, and the tab has no Add Page button at all. Detach the promoter to lose the events.
• A pending invitation already costs a slot. An invitation you have sent and nobody has answered occupies its place in the quota until it is accepted, declined or revoked. Three forgotten invitations on a five-slot plan leave you two.

Once the quota is full, + Add Page greys out and hovering it reads Page limit reached — upgrade to add more.

Add a page

1. Open the tab for the kind of page you want, then click + Add Page. A panel slides in from the right.
2. Confirm the Entity Type.
3. Type a name into Search. The hint states the reach of the search: Search any page: add the ones you manage, invite the ones managed by someone else, or claim a page that has no manager. With the box empty you see only pages you already manage.
4. Click a result. The panel checks who runs it, showing Checking this page... while it does.
5. Act on the answer. There are four of them, and the buttons at the bottom of the panel change to match.

Where an access request is on offer, a row of chips lets you pick exactly what you are asking for: View lineups and View page details. A Message (optional) box of up to 500 characters travels with an invitation.

Either way the page's own admin decides. You are sending a request, not taking anything.

What connecting a page to the crew grants

Attaching a page puts it under the crew, but it does not hand every member the keys to it. Two things happen.

The page inherits the crew's plan. Its features, quotas and storage come from the crew subscription from that moment on, which is why its own paid plan is cancelled on the way in.

Access is per member, per page, and you assign it. A crew role says what someone can do to the crew. What they can do on a page the crew manages comes from being assigned to that page. Nobody gets a page they were not put on.

Expand any directly attached page to see its assignment table, with columns Member, Role, Permissions and Actions.

1. Click the page row to expand it.
2. Click + Assign Member.
3. Pick the member. Only unassigned members appear.
4. Leave Custom feature override unticked to give them what their crew role already grants. The row then reads Inherits role.
5. Tick it to hand them a different set on this page alone. The hint says it plainly: Override the member's role features for this specific page only. The row then reads Custom with a count.
6. Click Assign Member.

The row menu offers Edit to change that choice later and Unassign to take the page away, which warns They will lose access to this page.

Because an override is per page, the same person can be a full manager on one artist and a read-only pair of eyes on another, without touching their crew role.

Shared with this crew

Pages that granted your crew access without joining it are listed separately, under Shared with this crew, with Access only — not counted in your page quota beside the heading. Each row shows the permissions you actually hold as chips and carries a Shared badge.

Request more opens a picker to ask for additional permissions. What you have already been granted is locked on and cannot be dropped from here, the request has to add at least one thing, and while one is outstanding the row reads Requested instead. Withdrawing an existing grant is the page admin's call, not yours.

Page invitations

Everything you have sent out sits under Page invitations, with columns Page, Status, Sent and Actions, and a status pill reading Pending, Accepted, Declined, Revoked or Expired. A pending invitation can be pulled back with Revoke, which also frees the quota slot it was holding.

Presskits

Headed Roster Presskits, with Manage presskits for all artists in your roster. underneath. Despite the wording, nothing is created or edited here. It is built as an index across the artists attached to the crew, with every action on it pointing out to the artist's own workspace.

Today it indexes nothing. Whoever opens it, the crew owner included, gets the same screen: the heading and its subtitle draw, and underneath them a red band carrying a server message that was never written for a reader, with a Retry button beside it. Retrying reproduces it. The per-artist rows, the presskit counts and the No artists in your roster empty state all sit behind that band, so none of them are reachable, and a crew with no artists attached lands on exactly the same band as a crew with twelve.

Two things stand in the way, and the first stops everyone before the second is ever reached.

The check behind the screen reads the crew role of whoever asked and looks for the roster presskit permission on it. That permission is not offered anywhere in the role feature picker, so no role you can build carries it, and the check has no owner exception written into it. Ownership of the crew does not substitute, and a member holding no role at all is refused by the same line.

Past that check, the screen resolves its artists through a link the database does not hold, so the list cannot be assembled even once the permission is sorted out.

Reach a presskit through the artist instead. Open the artist from Manage and use its own Presskits screen, which is a full editor and is unaffected by any of this. Building and publishing one is covered in Presskits.

The rail row follows the same permission, so only the crew owner sees it in a state that can be clicked at all. For everyone else it is greyed, with the silent hover described above.

API

Headed API, with Manage API keys and booking requests for this crew. Two tabs: API keys and Booking requests, the second badged with the number of submissions still marked New.

This is one of the two crew rows behind the plan gate as well as a feature, and the only one of them that opens. On a Basic crew it shows the upgrade panel; with the plan but without the API feature it shows Access Denied.

The keys themselves, their scopes and everything you can call with them are documented in the API section. Two habits worth carrying over from that section: the full secret is shown once at creation and never again, so copy it before closing the dialog, and Revoke takes effect immediately with no undo.

Where the rest lives