---
title: "Your team"
description: "Invite colleagues, what the two roles can do, and issuing API tokens."
---

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

# Your team

The Team page shows who belongs to your organization, and is where admins
invite new people and issue API tokens.

## Inviting someone

An admin invites a colleague by email from the Team page. The invitee opens
the link, chooses a password, and joins. One email address can belong to
more than one organization and switch between them without a second account.

## Roles

There are two roles, and the line between them is simple: a **member**
changes what a screen shows; an **admin** changes the screen itself.

| | Member | Admin |
|---|---|---|
| Upload media, edit playlists, assign content | yes | yes |
| Request screenshots, re-fetch content | yes | yes |
| Claim screens, rename them, reboot them | | yes |
| Invite people, manage the team | | yes |
| Issue and revoke API tokens | | yes |

## API tokens

An API token lets your own software put content on screens through the
[public API](/docs/api/), without a person or a browser. Issue one from
**Team → API tokens** as an admin. The secret is shown once — store it in
your integration's configuration, not in a document.

A token acts with a member's authority: it can change what screens show, but
it can never claim, reboot, or reconfigure a screen, invite anyone, or mint
another token. Every write a token makes is recorded under **Integration
activity** with the token's name, so you can always see which integration
changed a screen and when. Revoking a token takes effect immediately.

Source: https://anysign.tv/docs/team/index.mdx