# Team access
Source: https://docs.luriart.com/dashboard/team-access
Plain text: https://docs.luriart.com/dashboard/team-access.txt

Invite teammates, set their role, manage multiple client accounts as an agency, and remove access when someone leaves.

One Luria account belongs to one store (or one site). Inside it, as many people as you like can have access, each with a role that says what they can do.

## Inviting a teammate
1. In the dashboard, open **Settings > Team**.
2. Click **Invite**, enter their email, pick a role, and send.
3. They get an email with a link. If they don't have a Luria login yet, the link creates one.

Invites expire after 7 days; resend from the same screen if needed.

[Screenshot: Luria Settings > Team screen listing members with their roles and an Invite button]

## Roles
| Role       | Can do                                                                                                 | Can't do                                                                     |
| ---------- | ------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------- |
| **Owner**  | Everything: billing, approvals, settings, invite and remove anyone, delete the account.                | Be removed by anyone else. There's always at least one owner.  |
| **Admin**  | Approvals, Brand Brain, goals, connections, pause and roll back, invite and remove admins and viewers. | Billing, deleting the account, changing the owner.             |
| **Viewer** | See everything: results, tests, history, approvals queue.                                              | Change anything.                                                             |

A few practical notes:

* Give your copywriter or CRO person **Admin**. They'll be the one handling [approvals](/dashboard/approvals) and refining the [Brand Brain](/train/brand-brain).
* Give your finance person, or a stakeholder who just wants the numbers, **Viewer**.
* Give **Owner** to the person whose card is on file or who should be able to transfer it. You can have more than one owner.

To transfer ownership, the current owner opens the member's row and chooses **Make owner**.

## Agencies and multiple stores
If you manage several clients, each client gets their own Luria account: its own store, data, Brand Brain, billing, and team. This keeps client data cleanly separated and lets a client take their account with them if you part ways.

Your one login can belong to many accounts. Use the account switcher in the top left of the dashboard to move between them.

Two ways to set it up:

* **Client owns, you're admin.** The client creates the account (and puts their card on file), then invites you as Admin. Best when the client pays Luria directly.
* **You own, client views.** You create the account under your login and invite the client as Viewer or Admin. Best when Luria is bundled into your retainer. Billing lands on your card; see [Billing](/dashboard/billing).

Either way, the Luria account is tied to the store, not to whoever set it up, so ownership can be transferred later.

**Note:**
  If you use the [Luria Link](/connect/luria-link) extension in Meta Ads Manager, pick the matching client account in the extension before tagging ads, so the parameters point at the right Luria account.

## Removing access
Open **Settings > Team**, find the person, and click **Remove**.  Access ends immediately, including any sessions they have open.  Nothing they did is undone; their approvals and changes stay in History with their name on them.

If someone leaves with the only owner seat, contact support to reassign it; see [Contact support](/troubleshooting/contact-support).

## Security basics
* Every login is by email and password, with optional two-factor authentication under your profile.  Turn it on for owners at least.
* Sign in with Google is supported, so agencies on Google Workspace can skip passwords.
* Luria never shares one account's data with another, even when the same person is a member of both. More in [Security](/reference/security).

## Next steps
  - [Approvals](/dashboard/approvals)
  - [Billing](/dashboard/billing)
  - [Security](/reference/security)