Skip to main content

Members

What this is for

An organization is usually used by more than one person: a developer, a manager, maybe a contractor. The Members list shows everyone who belongs to yours and the role each person holds. A role decides what that person is allowed to do: for example, only owners and admins can create API keys. This page also explains each role in plain words so you know what to expect.

Before you start

  • Every member can open the list.
  • To add someone, see Invitations and roles. This page covers reading the list and understanding roles.

See your members

1

Open Organization settings

Select Organization settings at the bottom of the sidebar.
2

Select Members

Choose Members in the left menu.
3

Read the table

The card is headed Members and a line below counts them, for example “3 of 5 members on the Free plan”. The “of 5” part appears only when your plan has a member limit.

What you’ll see

A table named Members with three columns: If nobody has joined yet, the card shows No members with the line “Members appear here once they join.”

What each role can do

Controls you are not allowed to use are hidden or disabled, and the page tells you who can. For example you may see Only an organization owner or admin can create or revoke keys.

Common questions

The owner created the organization and can do everything, including deleting projects and renaming the organization. An admin manages day-to-day setup: keys, webhooks and projects. A member can look at data and watch activity but cannot change how things are set up.
The list shows the email each person signed up or was invited with. Names from the Profile page are not shown in this table.
Owners and admins use Invite member on this page to create a link and send it to the person. The steps are in Invitations and roles.
Your plan allows up to that many members. If there is no “of” number, your plan does not set a limit.
Roles are checked every time, not just by hiding buttons. Ask an owner or admin to do it, or to change your role.

Troubleshooting