TWG CLI Authentication Fails with "Access Denied" or "EAP Access Revoked"

Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.

Summary

Users attempting to authenticate or configure the Teamwork Graph CLI (TWG CLI) may encounter an "Access Denied" error, even if they were previously allowlisted or if EAP restrictions have been lifted. This is often caused by using an outdated version of the CLI that still enforces legacy Early Access Program (EAP) checks.

Diagnosis

When running twg setup or attempting to authenticate, the following error message appears:

✖ Access denied — credentials were NOT saved. Your TWG CLI EAP access has been revoked or is not enabled.

Cause

The TWG CLI previously required manual allowlisting for the Early Access Program. While many of these restrictions have been removed globally, older versions of the CLI client may still contain hardcoded checks or outdated authentication logic that triggers this error.

Solution

Updating the TWG CLI to the latest version typically resolves this issue, as newer versions align with the current backend authentication requirements.

Step 1: Check your current version

Run the following command to see which version you are currently using:

twg --version

Step 2: Update the CLI

Depending on your operating system, use the appropriate update method:

  • macOS (Homebrew):

brew update brew upgrade twg
  • macOS/Linux (Script): Re-run the installation script to fetch the latest binary:

    curl -fsSL --retry 2 https://teamwork-graph.atlassian.com/cli/install | bash
  • Windows: Download and install the latest version, following the documentation Set up TWG CLI

Step 3: Re-run Setup

After updating, clear any cached credentials and re-authenticate:

twg setup

Updated on September 23, 2026

Still need help?

The Atlassian Community is here for you.