Organizations

Members and roles

Every member of an organization has one of three roles, and the role determines what they may do. Members always have access to all of the organization's projects; the roles differ in who may manage the organization itself.

The three roles

Owner: The member who created the organization. The owner may do everything, and is the only role that may delete the organization or manage billing.
Admin: May do everything the owner may, except delete the organization and manage billing. Admins invite and manage members and have full access to every project.
Member: May work inside the projects: creating and editing monitors, prompts, brands, tags, and segments, and reading every response, source, and metric. Members may not invite users, manage the team, or touch billing.

Typically, you should keep a single owner, grant admin to the people who run the team, and give everyone doing the day-to-day monitoring work the member role. Since billing is reserved to the owner, the owner should be the person who holds the relationship with your finance team.

Inviting members

Owners and admins may invite new members by email, choosing the role at the time of the invitation. The invitee receives a link and joins by accepting it, signing in with the invited email address. Invitations expire if left unaccepted, and a pending invitation may be revoked at any time.

The number of members an organization may have is determined by its plan. A pending invitation counts toward the limit once accepted, not before.

Removing members

Owners and admins may remove a member from the organization. Removal takes effect immediately and revokes access to every project; nothing the member created is deleted, since monitors, prompts, and the rest belong to the project rather than to the person.

Roles and the API

API access uses its own permission model based on abilities granted to each key, which maps closely to what the member role may do. See API keys.