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

# Members and roles

> Invite people, choose what each person can do, and manage your organization's member list

Every person in a Basedash organization has one of three roles, Admin, Member, or View-only, which sets what they can do across the organization.

<Info>
  Available on all plans. Admins and members can invite people. Only admins can
  change roles or remove members.
</Info>

## Overview

Roles set the most a person can do. What they can open and edit within that limit depends on how each dashboard, chat, automation, and data source is shared with them or their [groups](/docs/administration/groups).

| Role | Description |
| - | - |
| Admin | Can access everything and manage organization settings, members, data sources, and billing. |
| Member | Can create and edit, subject to resource access. |
| View-only | Can open resources shared with them; can't create, edit, or chat. |

## Invite members

1. Open **Settings → Members** and click **Invite members**. You can also click **Invite teammates** in the sidebar.
2. In **Emails**, enter one or more addresses separated by commas.
3. Choose a **Role**.
4. Optionally, pick **Groups** to add the new members to. Only admins can assign groups.
5. Click **Send invites**.

Members can invite people as Member or View-only. Only admins can invite Admins. View-only members can't invite anyone.

To let coworkers join without an invite, turn on **Allow anyone with a verified @yourcompany.com email to join** in the **Joining** section of the Members page. See [Domains and login methods](/docs/administration/domains-and-login) for every way people can join.

## Roles

### Admin

Admins can do everything members can, plus:

* Have full access to everything shared in the organization, regardless of individual sharing settings
* Add, edit, and delete data sources, and control [who can query each one](/docs/administration/data-source-access-control)
* Invite admins, change roles, and remove members
* Create and manage [groups](/docs/administration/groups)
* Manage organization settings, including [AI context](/docs/features/ai-context), [skills](/docs/features/skills), feature settings, [security](/docs/administration/domains-and-login), and [audit logs](/docs/administration/audit-logs)
* Manage [billing and AI usage](/docs/administration/billing-and-ai-usage)

An organization always keeps at least one admin. The last admin can't be demoted, removed, or leave the organization.

### Member

Members can create and edit dashboards, charts, automations, and models, chat with AI, and invite new members or view-only members. What they can open and edit depends on [dashboard sharing](/docs/features/dashboards#sharing-and-collaboration) and [data source access](/docs/administration/data-source-access-control).

### View-only

View-only members can open what's been shared with them, but can't create or change anything. Use this role for people who only need to read dashboards.

View-only members can:

* View dashboards, charts, insights, automations, and chats they have access to
* Change dashboard filters, drill down into charts, and export chart data
* Manage their own profile, favorites, and personal API keys

View-only members can't:

* Chat with AI, including from Slack or the MCP server
* Create or edit dashboards, charts, automations, or models
* Write their own SQL; they can only run the saved queries behind charts
* Share dashboards or invite people
* Make changes through the public API or the MCP server (read-only requests still work)

View-only limits a person's existing access rather than replacing it. If they have edit access to a dashboard, they can still only view it. Their access is kept, so changing them back to Member restores what they had before.

## Manage members

The Members page lists everyone in the organization, with admins first. Use **Search members…** to find someone, and the filter menu to show **Active**, **Invited**, or **Removed** people. Badges show each person's role, whether they're invited or removed, and how many groups they're in.

Open the menu on a member's row to:

* **Copy email**
* Add or remove them from **Groups** (admins)
* **Change role** (admins; not for yourself)
* **Remove** them from the organization (admins)
* **Restore** a removed member (admins)
* **Revoke invite** for someone who hasn't joined yet (admins)

To leave an organization, open the menu on your own row and choose **Leave organization**.

## API

Admins can list, invite, update, and remove members with the [public API](/docs/api-reference/members/list-members). Inviting through the API sends the same invite email as the app.

## FAQ

<AccordionGroup>
  <Accordion title="What happens to a removed member's work?">
    Removing a member deactivates them instead of deleting them, so you can
    restore them later from the **Removed** filter on the Members page.
  </Accordion>

  <Accordion title="Can I resend an invite?">
    There's no resend button. Revoke the invite from the member's row, then
    invite the same email again.
  </Accordion>

  <Accordion title="Can I provision members from my identity provider?">
    Yes, on the Enterprise plan. Use [SCIM](/docs/administration/scim) to create,
    update, and remove members and groups from Okta or Microsoft Entra ID.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Groups" icon="users" href="/docs/administration/groups">
    Organize members for sharing, data access, and AI context.
  </Card>

  <Card title="Data source access control" icon="lock" href="/docs/administration/data-source-access-control">
    Choose who can query each data source.
  </Card>

  <Card title="Domains and login methods" icon="right-to-bracket" href="/docs/administration/domains-and-login">
    Control how people sign in and join.
  </Card>

  <Card title="SCIM" icon="arrows-rotate" href="/docs/administration/scim">
    Provision members from your identity provider.
  </Card>
</CardGroup>


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