# Team management

{% hint style="info" %}
**Available in Stratix Premium.** This surface is part of the logged-in workspace at [stratix.layerlens.ai](https://stratix.layerlens.ai). Stratix Public users can browse the catalog but cannot use this feature.
{% endhint %}

The Team management surface in Settings is where Admins invite teammates, set roles, and watch seat utilization for the active org.

URL: [`stratix.layerlens.ai/dashboard/settings/team`](https://stratix.layerlens.ai/dashboard/settings/team)

## Roles

* **Admin** — can manage members, billing, integrations, and all data
* **Editor** — can create and modify all data; cannot manage members or billing
* **Viewer** — read-only access to org data
* **Custom roles** — Enterprise tier supports custom role definitions

## Inviting teammates

1. **Settings → Team → Invite**
2. Enter email + role
3. The invitee receives an email with a link to join the org
4. They sign in (or sign up) and land in the active org with the assigned role

## Removing or changing a role

* Click any member's row → **Edit** to change role
* Click **Remove** to revoke their access (their evaluations and other artifacts remain in the org)

## Seat utilization

The Team page shows current usage against your seat allotment (for tiers with seat caps). Free and Premium PAYG don't impose hard seat caps; Enterprise contracts can.

## Audit

Admin actions (invite, role change, removal) are logged in the audit log. Enterprise tiers retain audit logs for the contractual period.

## Where to next

* [Organizations and multi-org](/11.-admin/organizations.md)
* [Settings](/11.-admin/settings.md)
* [Enterprise](/11.-admin/11-admin.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.layerlens.ai/11.-admin/team-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.