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

# Team and roles

> Invite members, change and remove them, and create the role templates analysts and engineers use.

export const props_0 = undefined

export const Clip = ({id, caption}) => <Frame caption={caption}>
    <video controls muted playsInline preload="metadata" className="w-full aspect-video rounded-xl" poster={`/videos/guides/${id}.poster.png`} src={`/videos/guides/${id}.mp4`} />
  </Frame>;

export const Shot = ({id, alt, caption}) => <Frame caption={caption}>
    <img className="block dark:hidden rounded-lg" src={`/images/guides/${id}.light.png`} alt={alt} loading="lazy" decoding="async" />
    <img className="hidden dark:block rounded-lg" src={`/images/guides/${id}.dark.png`} alt={alt} loading="lazy" decoding="async" />
  </Frame>;

**Team** at [`/team`](https://console.us.frayme.io/team) has three tabs: **Team Members**, **Roles & Permissions**, **Activity Log**.

<Shot id="admin/team-01-overview" alt="Team page" caption="Members with their roles." />

<Clip id="admin/create-role-and-invite" caption="Create a role from the analyst template and invite a member." />

## Invite a member

<Steps>
  <Step title="Click Invite Member">
    Enter **Full name**, **Email address** and choose a **Role**. The role cannot be changed on the invitation once sent.

    <Shot id="admin/team-02-invite" alt="Invite team member dialog" caption="Pick the role at invitation time." />
  </Step>

  <Step title="Send invitation">
    **Invitation sent** confirms. The invitee opens the link, signs in with that email and lands in your tenant with the chosen role.

    <Shot id="admin/team-03-invite-toast" alt="Invitation sent" caption="Pending invitations are listed until accepted." />
  </Step>
</Steps>

## Change a member's role

The row menu → **Edit** opens **Edit Team Member** with name and email read-only and a **Role** select.

<Shot id="admin/team-04-edit-member" alt="Edit Team Member dialog" caption="Only the role changes." />

## Remove a member

The row menu → **Remove** asks **Remove team member**. The member loses access immediately; their past decisions stay attributed to them.

<Shot id="admin/team-05-remove-confirm" alt="Remove team member dialog" caption="Confirmed removal." />

## Roles and permissions

Every role with its member count and description. **admin** is reserved and cannot be edited.

<Shot id="admin/team-06-roles" alt="Roles & Permissions tab" caption="The reserved admin role plus your templates." />

## Create a role

**Create Role** asks for a **Name** (lowercase letters and hyphens, starting with a letter), a **Description** and the **Permissions**, grouped by the scope catalog with the read and write tiers side by side.

<Shot id="admin/team-07-create-role-empty" alt="Create Role dialog" caption="Scopes grouped by area." />

You can only grant scopes you hold yourself; the admin role holds them all.

<Shot id="admin/team-10-role-name-error" alt="Role name validation" caption="Names are lowercase letters and hyphens." />

## Recommended role templates

<Tabs>
  <Tab title="analyst">
    Tick **Write** under **Cases**, and **Read** under **Queues**, **Communications** and **Team**.

    <Shot id="admin/team-08-role-analyst" alt="Analyst template" caption="The analyst template." />
  </Tab>

  <Tab title="senior-analyst">
    The analyst template plus **Write** under **Case override** and **Risk**.
  </Tab>

  <Tab title="engineer">
    Tick **Write** under **Workflows**, **Data sources**, **API keys**, **Webhooks**, **Risk**, **Attributes** and **Cases** (needed to submit test cases from the builder), and **Read** under **Queues**, **Communications** and **Team**.

    <Shot id="admin/team-09-role-engineer" alt="Engineer template" caption="The engineer template." />
  </Tab>
</Tabs>

## The invitation link

The invitee lands on **You're invited** and clicks **Sign in to accept**. If the link is invalid or expired the page says so; send a new invitation.

## Not available

<Note>
  **Not available today.** {props_0.what} appears in the interface but does nothing yet. The guides only document controls that work; this note marks the gap so you do not wait on it.
</Note>

There is no deactivate and no resend-invite action; remove and invite again instead.