# Team and client access

> How to invite teammates, what owners, admins, members and viewers can do, how per-project access works, and how to give clients access.

## How teams work

Everything in Rankfinity belongs to a **team** (your workspace): projects, credits and connections. When you sign up, you are the **owner** of your own team. Invite colleagues and they work on the same projects and spend from the same credit wallet.

One person belongs to one team. This keeps the answer to "whose data am I looking at?" always clear.

## Roles

| Action | Owner | Admin | Member | Viewer |
|---|---|---|---|---|
| See the team's projects, reports, scans, AI results | Yes | Yes | Yes | Yes |
| Create and edit projects | Yes | Yes | Yes | No |
| Run scans and spend credits | Yes | Yes | Yes | No |
| Delete projects (to Recently deleted) | Yes | Yes | Yes | No |
| Invite people, change roles, remove members | Yes | Yes | No | No |
| Rename the team | Yes | Yes | No | No |
| Buy credits, see invoices | Yes | No | No | No |
| Manage own profile, password and data export | Yes | Yes | Yes | Yes |

The owner cannot be demoted or removed, so a team always has someone who can invite, pay and delete.

## Inviting someone

1. Open **Settings › Team**.
2. Under **Invite someone**, enter the email and choose the role: a **member** can work on projects and run scans; a **viewer** can only read.
3. Optionally limit which projects they get (see below).
4. Click **Send invitation**.

The person receives an email with a link. If email cannot be sent, the screen shows the link so you can send it yourself. **Pending invitations** lists invitations not yet accepted; **Revoke** cancels one.

## Per-project access

By default every member sees **all projects**. Click **Access** on a member's row (or set it in the invitation) to choose, project by project:

- **View only** or **View and edit**.
- **Spend credits (run scans)** — whether they may start paid actions on this project.
- **See and send reports**.
- **Change project settings**.

**Reset to all projects** returns to the default. A project a member cannot access simply does not exist for them — it does not appear in lists, links or search.

### What "view only" blocks

A view-only person can open every screen of the project and read every result. They cannot change settings, keywords, branding or sharing, start scans, use paid tools, or use the AI chat on the project (it spends the team's credits). They can still manage their personal things: their own email preferences, their own lookups and their own chat history.

## Seat settings

Each member's row also has notification options: **Rank alerts**, **Finished runs**, **Credits & billing**, and **May spend credits**. Save with the row's button.

## Team activity

**Team activity** lists what members did and when: scans started, projects created, links shared, settings changed. **Download CSV** exports it.

The ledger remembers which member spent credits, so the owner can see who used what in **My account › Activity**.

## Clients

Agencies have two ways to give a client access:

1. **Client links** — a read-only page with the project's key numbers, no login needed. Create it in **Reports › Client links**. See [Client reports and sharing](/docs/reports). For most clients this is enough.
2. **Client accounts** — a login with the **client** role. A client sees only the projects shared with them.

What a client can and cannot do:

- Can view the shared projects, reports, results and stored data, and download exports.
- Can manage their own email preferences, including crawl reports and alerts for the shared projects.
- Cannot start anything that spends credits, change schedules, add keywords that would start scans, change project settings, create keys or connections, or reply to reviews.
- Never sees credits, prices or billing — "Billing is handled by your agency".
- Does not see the AI chat.

## Removing someone

Click **Remove** on the member's row. They lose access immediately. Their work (projects, scans, reports) stays with the team.

## Common questions

**Can a member see our invoices?**
No. Only the owner buys credits and sees invoices.

**Do members have their own credits?**
No. The team shares one wallet. Use **Spend credits** per project to control who can spend.

**Can a person be in two teams?**
No. One person, one team. Use another email address for a second team.

**A member says a project is missing.**
Check **Access** on their row; the project may not be in their list.

**Can a viewer export data?**
Yes. Viewers can read and export; they cannot change or spend.