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

# Team access

> Invite people and choose Admin, Member or Viewer permissions.

export const Screenshot = ({light, dark, alt, caption, width, height, sizes, portrait = false}) => <figure className={portrait ? "oss-doc-screenshot oss-doc-screenshot-portrait" : "oss-doc-screenshot"}>
    <div className="oss-product-light">
      <img src={light} alt={alt} width={width} height={height} sizes={sizes} loading="lazy" />
    </div>
    <div className="oss-product-dark">
      <img src={dark || light} alt={alt} width={width} height={height} sizes={sizes} loading="lazy" />
    </div>
    {caption ? <figcaption>{caption}</figcaption> : null}
  </figure>;

Rootset serves one workspace per installation. Admins manage its people in **Team Settings → Members**. Invite a person by email and choose their role; SMTP delivers the invitation.

| Role | Permissions |
| - | - |
| Viewer | Read tables and cell history, filter data, and request exports. |
| Member | Viewer access plus create/edit databases, tables and fields, manage unique rules, and create/edit/delete rows. Cannot delete databases or tables. |
| Admin | Member access plus delete databases/tables, manage people and team API keys, and administer the installation. |

A person's current role applies to their browser session, personal API keys and OAuth connections. API permissions cannot elevate a person beyond their role. Team API keys belong to the workspace and are managed by Admins; they do not depend on the creator remaining a member.

Database deletion in the browser asks an Admin to confirm their identity with a password or passkey. Other authorised operations execute directly; there is no approval-ticket workflow.

<Screenshot light="/assets/screenshots/team-access-light.png" dark="/assets/screenshots/team-access-dark.png" alt="Team members and roles in Rootset" width={3840} height={2160} />


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