DOCUMENTATION / Team access

Team Trigger setup

Request team access to the existing 10Signals Trigger project.

Runs on

The team's existing Trigger project and approved environment

Before you start

Approval from the 10Signals team and an environment key supplied securely

Which key do I need?

1. 1

   Request access from the team

   Contact your 10Signals team administrator before configuring the CLI. Explain who or which agent will use it and the intended work. Do not post API keys in the request.

   You should see The team confirms whether you are authorized to use its existing project.

2. 2

   Confirm the project and environment

   The team selects the approved project and environment, and supplies the environment key through its approved secret-sharing channel. Ask for a Trigger dashboard invitation only if you need to inspect runs. A dashboard invitation and the CLI environment key are different forms of access.

   You should see You know which environment is approved and how to receive its runtime key securely.

3. 3

   Install and connect the CLI

   After approval, follow the Windows or macOS CLI guide. Enter the team-issued key only at configure's hidden prompt. You do not need to create a project, deploy tasks, or obtain a deployment PAT.

   Install the team CLI ↗
4. 4

   Verify the installed tools

   Run doctor after configuring the client. If tasks, a promoted worker or provider configuration are missing, ask the team to fix the environment. Do not deploy or change the project's settings yourself.

   You should see COMPLETED and status ready. This checks the connection and tasks, not a completed research report.

5. 5

   Run approved work and manage access

   Use report for the agreed research; it returns progress and results in the same command. Keep the run ID if interrupted. Ask the team to revoke or rotate project access when it is no longer needed; logout removes only your local saved key.