Skip to main content
Adding the team is the moment a brand atlas starts to do real work. A populated atlas with no team is a private notebook; a populated atlas with the right team in place is a working system. This page walks through inviting team members, choosing roles, and what each role can do.

Before you start

You will need:
  • The email address of the person you want to invite.
  • A clear sense of whether they should read only or have edit rights.
  • A team seat available on your tier (seat limits are listed on the tier pages).

Step by step

1

Open Team settings

Go to Settings → Team. You will see the current team members listed, with their roles and the date they joined.
The Team settings screen showing the current team list.
2

Click Invite team member

A short form opens. Enter the email address. Choose the role.
3

Choose the right role

Brand Atlas has three roles:
  • Brand owner. Full edit rights. Approves Update Requests. Manages billing and team. Only one person per atlas at a time, transferable.
  • Editor. Edit rights on the standard sections and Horizons they have been granted access to. Cannot approve Update Requests. Available on Keeper and Guardian.
  • Team member. Read access to the atlas. Can search, copy values, and raise Update Requests on Keeper and Guardian.
Most invitees are Team Members. Editors are typically internal brand managers or MadeBy_ collaborators given delegated edit rights. The brand owner is the founder or accountable role; transferring that is a separate action covered on the Account and profile page.
4

Send the invite

Click Send invite. The invitee receives an email immediately with a link to set up their account. The link expires after seven days; if it expires, resend from the team list.
5

Confirm they have access

Once the team member accepts, they appear in the team list as Active. Ask them to confirm they can sign in and read the populated sections. If they cannot, see Team member cannot see a section.

How many team members to invite

Start with the people who use the brand most often, not the people who oversee it most senior. A useful first cohort:
  • The marketing manager (or equivalent).
  • The social manager.
  • One freelance or agency contributor the team works with regularly.
  • Any internal designer who has rights to edit.
That cohort generates most of the questions that improve the atlas. Senior reviewers can be added later; their use of the atlas is usually less frequent.

Inviting people who only need a single section

For a vendor who needs the colour system to print, or a partner who needs the logo lock-ups for a press release, a Guest Pass is the right tool, not a team seat. Guest Passes are time-limited and scope-limited, and they do not count against the seat limit on your tier. See Guest Passes explained.

What team members can do on each tier

Team Members can read the populated sections. They cannot raise Update Requests on Scout. The atlas works as a shared read-only resource.

Removing or pausing a team member

Open Settings → Team, find the person, click the menu, choose Pause or Remove. Pause keeps the seat but suspends access; useful for a freelancer between engagements. Remove releases the seat. Both actions are reversible; the brand record retains the history of the team membership either way.

Roles and permissions

What each role can do, in detail.

Guest Passes

For people who need part of the atlas, not all of it.

Team and seats

The full settings reference.