====
Team
====

Eyrie supports multi-user collaboration on projects with a role-based access
model.

Project Roles
=============

Every project member has one of three roles:

- **User** — read-only access to deployments and logs.
- **Developer** — can create and manage deployments, trigger deploys, and
  access admin pages (subject to scope ``role_to_admin`` settings).
- **Admin** — full access including deployment group management and project
  settings.

The project **owner** has implicit admin privileges and is the only user who
can delete deployment groups or transfer ownership.

Inviting Users
==============

1. Open your project and navigate to the **Team** panel.
2. Click **Invite**.
3. Enter the user's email address and select a role.
4. Click **Send Invite**.

If the email does not belong to an existing Eyrie user, a portal account is
created automatically and the user receives an invitation email.

.. image:: /static/img/team_panel.png
   :alt: TODO — screenshot of the team panel

.. image:: /static/img/invite_form.png
   :alt: TODO — screenshot of the invite form

Accepting / Rejecting Invites
==============================

Invited users see pending invitations on their dashboard. They can **accept**
to join the project or **reject** to decline.

Deployment / Group-Level Role Overrides
========================================

For fine-grained control, you can assign a user a different role on a specific
deployment or deployment group. For example, a *user* at the project level
might be granted *developer* access on a single development deployment.

Owner-Only Capabilities
========================

Only the project owner can:

- Delete a deployment group.
- Remove other admins.
- Transfer project ownership.
- Block portal access to the project.