Teams & auth

Everything you create in Evident is shared with your team. Here's how teams, roles, and authentication work.

Evident is built around teams. Every runner, conversation, and integration belongs to a team, and your teammates see the same things you do. This page covers how teams are created, what each role can do, and how you sign in — from the web and from the command line.

Your work is scoped to your team

  • When you use Evident, you only see the runners and resources that belong to your team.
  • You need a team to use Evident. If you're signed in but have no active team, you're told you need one before you can continue.
  • Your team is set up automatically the first time you use Evident — you can start working right away, no manual setup step.

Collaboration

Runners are shared across the whole team. If a teammate creates a runner, you see it in your runner list, and vice-versa. The same is true for the team's Slack connection and its settings.

  • Joining a team gives you access to its runners straight away.
  • Leaving (or being removed from) a team removes your access to its runners.

Roles & permissions

Teams have three roles: owner, admin, and member. Most day-to-day work is open to everyone on the team, but a few actions that affect the whole team are restricted to owners and admins.

  • Everyone (members, admins, owners) can see the team's runners, open their chat, and message them from Slack.
  • Only admins and owners can delete runners. A regular member who tries is not allowed to, and the runner remains.
  • Only admins and owners can disconnect Slack — it's a team-wide action. A regular member who tries is told they don't have permission, and the connection is unchanged. (See Slack integration.)

Per-team isolation

Each team is isolated from every other team. A team's Slack connection, its runners, and its conversations are its own — they're never visible to, or reachable from, another team. If you belong to more than one team, connecting Slack for one team has no effect on the others, and a newly created team starts with no Slack connection at all.

Reaching a runner's chat

Each runner has its own chat surface, reachable on its own address. Access is controlled by team membership:

  • If you're on the team that owns the runner and signed in, you're let straight through.
  • If you're signed in but not on that team, you're refused access — and nothing reaches the runner.
  • If you're signed out, you're sent to sign in first before anything reaches the runner.
  • If you lose access (e.g. you're removed from the team), that takes effect promptly.

Signing in from the command line

The Evident CLI runs your runner on your machine. To sign it in, run the sign-in command: 

evident login

You're shown a link and a short code to confirm in your browser. While you confirm, the command waits and tells you it's waiting. Once you confirm the code, the command signs you in and stays signed in for your later commands — and it acts on your team automatically, without you having to choose one.

If you start signing in but never confirm the code, it eventually expires and you're asked to start again.

Runner keys

A runner key is a credential scoped to a single runner. Anything that connects using that key is treated as that runner and limited to that runner's team. A runner key lets the Evident CLI on your machine connect as that runner, without an interactive login — handy for headless or automated setups. With EVIDENT_RUNNER_KEY set, evident run doesn't even need --runner: it resolves the runner from the key. You manage runner keys from the API Keys section of the runner's settings in the Evident app.

Next steps