> ## Documentation Index
> Fetch the complete documentation index at: https://soran.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Members and roles

> Invite your team and control what each person can reach.

Access is granted at the organization, and every invitation answers two
questions: **what this person may do**, and **where they may do it**.

## Inviting someone

You are not asked to pick a role when you invite. Everyone enters at the entry
role, whose baseline is shown to you, and a grid decides the rest — what they may
do, and which properties it applies to.

This is one question asked once. Offering a role *and* a permission grid would
ask the same thing in two vocabularies and let the two answers disagree.

## Promoting someone

Making someone an admin or an owner happens on the members list, where the person
is already in front of you, rather than in the invitation.

## The same model as keys

Permissions work the same way for API keys as for people: the same two questions,
the same grid. A key is scoped, not all-powerful.

> [!NOTE]
>
> Because data is scoped to properties, granting access to one property grants
> nothing in another. See [Properties and
> organizations](/docs/concepts/properties-and-organizations).

## Related

> **[API keys](/docs/account/api-keys)**
>
> Scoped keys for programmatic access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.