Team and Permissions

Every page on Sway has one owner and any number of teammates, and each teammate carries a list of individual permissions rather than a single rank. This screen is where that list is written, changed and taken back.

Where the screen lives

The screen is the same on four page types, with the same heading and the same dialogs. Only the tick boxes it offers differ, because a venue has no ticketing and an artist has no line-up.

Open the screen

1. Open Manage, then click the page you want.
2. Click Permissions in the left sidebar, under the Access heading.

The heading reads Permission Management, with Manage team members and their feature access. underneath and an Add User button on the right.

Read the table

Three cards sit above the table: Members, counted against your plan's ceiling, Tier, and Crew, which only appears when the page belongs to a crew.

The table itself has four columns, User, Role, Features and Actions, and the last one is only drawn for people who can actually change something. Small badges follow the name: Owner, Crew for access that arrives through a crew, and You on your own row. A search box filters on Search by name or email..., and the select beside it, whose first option reads All levels, filters on the role badge.

The Role badge is worked out on the spot, not stored. Sway compares the member's exact feature list against its built-in roles and prints Admin, Manager, Editor or Viewer only when the two match to the letter. Anything else reads Custom followed by the number of features held. In practice most members read Custom, including people you added straight from a role template, because the templates offered in the dialog and the roles the badge compares against are not the same lists. Read the number, and open the row if you need the detail; the word is decoration.

Add someone to the team

1. Click Add User. The dialog opens under Search for a user and configure their feature access.
2. Under Select user, type at least two characters into Search by username or email.... Until you do, the panel reads Start typing to search for users., and a search that finds nobody answers No user found.
3. Click the person in the list. Only the first six matches are shown, with Showing first 6 results. underneath when there are more; narrow the search rather than scrolling.
4. Pick a Role template on the right. The dialog opens on the viewer template, and every option names the template and how many permissions it carries.
5. Adjust the tick boxes if you want something else. Ticking or unticking any box flips the select to Custom role, and it leaves whatever the template already put in place rather than starting from nothing.
6. Click Add Member. It stays disabled until both a person and at least one permission are selected. A Member added successfully. confirmation appears and the row joins the table.

There is nothing to accept. The person is not sent an invitation: their access starts the moment the dialog closes, and the page appears in their own Manage list on their next visit.

What the tick boxes cover

Permissions are grouped by area, and each group holds a plainly named pair or trio such as View orders, Manage orders and Export orders.

A counter beside the boxes tracks the total as selected, so you can see at a glance how far a template reaches.

Change what someone can do

1. Click the pencil icon on their row. Edit Features opens above Update feature access for and their name.
2. Choose a different Role template, or tick and untick individual boxes.
3. Click Save. The confirmation reads Member features updated.

Saving rewrites the whole list. What is ticked when you press Save is what the member has afterwards; unticking a box takes that permission away immediately, with no further confirmation.

The three permissions above are the exception, and the exception is worth remembering. Because they are not drawn on screen, editing a member neither adds nor removes them: someone who received them with a broad template keeps them through every later edit. The only way to strip them is to pick a template that does not carry them, which rewrites the list from the template's own contents.

Remove someone

1. Click the bin icon on their row.
2. The Remove Permission dialog says You are about to remove access for, names the person, and adds This user will no longer have access to this event. That last line is shared across all four page types, so it says "event" even on an artist, venue or promoter page.
3. Click Remove Permission. The confirmation reads Member removed.

Rows you cannot act on

Three kinds of row show a sentence where the buttons would be:

• The page owner, marked Owner (protected). Ownership is not transferred from this screen.
• Your own row, marked You cannot edit your own permissions. You cannot lock yourself out, and you cannot promote yourself either.
• Anyone whose access comes from a crew, marked Crew-managed page. Change it in the crew, not here.

A member who has both a direct list and crew coverage carries an amber + Crew badge in the Features column. Hovering it opens Permission merge, which breaks the total into Direct:, Via crew ({name}): and Effective (merged):, notes how many were added from crew or overridden by direct, and states the rule underneath: Direct permissions take priority per domain; crew fills in uncovered domains.

Crews, shared access and co-organizers

On artist, venue and promoter pages, three further blocks sit between the header and the stat cards. The event screen carries none of them: it shows only a Crew-managed page notice when the event belongs to one.

A crew invitation arrives as a banner headed Crew invitation, reading wants to add this page to their crew, with Accept and Decline. Read the consequences before accepting: the page leaves any paid plan it holds and inherits the crew's, and the crew's members may gain rights to edit or delete it.

A page already in a crew shows the Crew-managed page notice with a Leave crew button beside it. The confirmation, Leave this crew, is blunt about the part people miss: the page's own paid subscription was cancelled when it joined and leaving does not bring it back, so you would have to subscribe again.

Crews you granted access to are listed under Crews with access, described as crews that do not own this page and are not billed for it. Each row shows Access granted on {date} and pills naming exactly what the crew can do. Edit permissions opens a side panel with the same switches, under a note reading The crew keeps its own plan; you can revoke at any time. Withdrawing takes one click: Revoke ends the access straight away, after a Revoke access confirmation.

The cap is not a matter of what you happened to tick. A share is checked against a fixed list when it is written, and checked again every time the crew's access is worked out, so it can never reach your settings, your billing or your member list, whatever roles the crew has given its own people.

On a promoter page only, two extra controls handle events run with someone else. An Event invitation banner offers Accept or Decline on a request to co-organize, and Stop co-organizing pulls the promoter back out of an event it had accepted, which removes it as a public co-organizer and drops its admins' access to that event on the spot. Accepting or leaving never changes who receives ticket money; that lives on the payout account, described in Connect Payouts.

How many members you can have

The Members card shows a count against a ceiling that comes from the page's plan. Once you reach it, Add User greys out and hovering it reads Member limit reached. Upgrade your plan to add more members.

Who can open this screen

Two permissions govern the screen itself, one to read it and one to change it. With the reading one, the table is fully visible but the Actions column is not drawn at all. With neither, but with any other permission on the page, the table is still readable, since the screen only refuses people who hold nothing at all. Those land on Access Denied and You don't have permission to access this page.

Page owners hold both, which is why a brand-new page always has someone who can build its team.

Crews work differently

A crew is a team that manages several pages at once, and it does not use this screen. It has Members, where each person is given one crew Role, and Roles, where those roles are defined once and reused. Editing a role changes what every member holding it can do, everywhere, immediately.

The two models meet on the page: a crew's coverage shows up here as rows marked Crew-managed page, and where the crew was granted access rather than ownership, as a row under Crews with access.

Where the rest of this lives