Docs

Team and access

Updated Sep 22, 2026
/docs/brands/team-and-access.mdView as Markdown

Who can do what in an organization — members and invitations, the role library, access grants and their scopes, teams and team rosters, and what a plain member sees.

Reading an organization's accessVideo coming soon

Access in Relish is built from three things: members (the people), roles (what a set of permissions is called), and grants (a role given to a person or team at a specific scope). Teams group members so one grant can cover several people.

What this is and when to use it

Use it when:

  • A colleague needs to work in your organization and you need them invited.
  • Someone's access should cover one brand instead of the whole organization.
  • You need to see what a person can currently do before changing it.
  • You use teams to give a group the same access in one move.

Do not use it to:

  • Manage an organization's own identity — name, logo, slug, or invite policy — which is Organization settings.
  • Invite a creator to a campaign — that is Invite creators to a campaign.
  • Change what a campaign does — access governs who may act, not what acts happen.
Members, roles, grants, and teamsVideo coming soon

Members

Open Access from the organization menu, or Access in the organization settings rail. The Members tab is the roster.

  1. Read the roster: each row carries the member's name, email, organization role, joined date, and the roles they hold on brands and campaigns.
  2. Select the member's roles chip to open the Assignments tab filtered to their grants.
  3. Select Invite to add someone new.
  4. In the Invite members dialog, type the email addresses under Email addresses — press Enter or a comma after each one, and add as many as you need.
  5. Choose the Role the new members get in the organization.
  6. Optional: choose a team under Add to team for members who should inherit that team's access.
  7. Select Send invitations. The dialog reports what happened per address, and each invitation appears under Pending invitations.

An address that is not a valid email is refused inline — 1 invalid email — remove it to send. — and the send button stays disabled until it is fixed.

Pending invitations

Invitations to the organization appear under Pending invitations until they are accepted or expire, with the columns Email, Invited, Expires, and Role. The card is a record: it does not offer resend or cancel, so treat the list as read-only and invite again only if an invitation is genuinely needed.

Remove a member

  1. Open the row's Remove control.
  2. Read the confirmation: the person loses access immediately, and the action cannot be undone.
  3. Decide whether to also revoke their brand and campaign access — the dialog offers a checkbox that revokes their grants before removal, and counts them.
  4. Confirm to remove.

Roles

The Role library tab lists the preset roles Relish defines — Organization Manager, Brand Lead, and the rest — each with the capabilities it carries and the scopes it can be granted at. Presets are not editable.

Build a role from capabilities

Creating, editing, and archiving a roleVideo coming soon
  1. Open the Role library tab.
  2. Select New role.
  3. Give the role a name and an optional description.
  4. Toggle the capabilities the role should carry in the capability matrix.
  5. Select Create role. The role appears under custom roles with its capability summary and the scopes it can be granted at.

Change or retire a role

  1. Select Edit on the role's row, toggle the capabilities you need, and select Save changes.
  2. Select Archive on the row to retire a role.
  3. Confirm Archive this role? — an archived role can no longer be assigned, and the change cannot be undone.

IMPORTANT — Archiving a role removes it from the library but keeps its name reserved. Creating a new role with the same name afterwards is refused — choose a distinct name.

Assignments (grants)

The Assignments tab is where a role meets a person or a team at a scope. It also lists the organization's Default access — the grant every member holds automatically when they join, which cannot be revoked.

Give someone access

  1. Open the Assignments tab.
  2. Select Assign access.
  3. Who gets access — choose the member, or the team, that receives it.
  4. Which role — choose the role. The role's capabilities decide which scopes are offered.
  5. Where — choose the scope: the entire organization, one brand, one campaign, or one location. For a brand or campaign, search for and select it.
  6. Expiry — leave it as No expiry, or set an end date for temporary access.
  7. Confirm the assignment. The grant appears in the list.

Filter the list

Use the scope filter, the assignee filter, and the search box to find a grant before acting on it — for example, filter to one brand to see exactly who can act on it.

Revoke access

  1. Find the grant in the list.
  2. Select Revoke on its row.
  3. Read the confirmation, which names the role, the person, and the scope, then confirm. The person loses those permissions immediately.

The system-managed default-access grant has no revoke control — it is held by everyone by design.

Teams

Teams let one grant cover several people. They also carry their own owner/member roles.

  1. Open Teams from the organization menu, or from the organization settings rail.
  2. Select Create team, name it, and confirm. The team appears in the list.
  3. Open the team, then the Members tab, to see its roster.
  4. Select Add to team, pick the organization member, and choose whether they join as owner or member.
  5. Change a member's team role from the roster's role control.
  6. Remove a member with the roster's Remove control and its confirmation.
  7. Select Delete team on the team page to remove the team. The confirmation requires typing the team name, and it states that grants pointing at the team must be revoked first.

WARNING — A team must keep at least one owner. The last owner's role control and remove control are locked until another member is promoted — the control says exactly that when you hover it.

What a plain member sees

Access screens are honest about who may change things. A member without the management capabilities sees the same data — the roster, the roles, the grants, the teams — with the editing controls disabled and a line explaining that Relish manages that surface.

That is deliberate: the data is not hidden, the actions are. If you need a change made on a surface you cannot edit, ask an organization owner or contact Relish.