How can we help?

Getting started with NeetoAuth CLI

Imagine onboarding a new teammate and setting the right access without jumping across multiple pages in the NeetoAuth UI. You send the invite, choose roles, double-check product permissions, and want to confirm everything is configured correctly.

With NeetoAuth CLI, you can handle that flow from one place: your terminal. You can invite users, assign roles, inspect available product roles, and run a quick health check. When you manage multiple users or multiple workspaces, this command-based flow is easier to repeat than manually going through the same screens every time.

What is NeetoAuth CLI?

NeetoAuth CLI is the command-line interface for managing team members and product roles in your NeetoAuth workspace.

Authentication happens through a browser login flow. After login, the CLI stores your session credentials locally and uses them for subsequent commands.

Why this is useful

Think of NeetoAuth CLI as handling workspace access from one command-driven control panel instead of clicking through multiple screens.

A few examples of what becomes possible:

  • You need to onboard someone quickly, so you invite them and assign their role in one command.

  • You want to confirm product-level permissions before granting access, so you list available roles first.

  • You have to add multiple teammates, so you repeat the same command flow instead of manually redoing UI steps.

  • You want repeatable ops, so you use JSON output in scripts or AI-assisted workflows.

  • You want to do the same set of actions across multiple workspaces you manage, and you can do it with the CLI instead of manually going through the same screens in each workspace.

You do not need to be deeply technical to benefit from this. If you already use simple terminal commands, you will be able to get started with NeetoAuth CLI much more easily, since the commands follow the same patterns you use every day.

What you need to get started

  1. Access to one or more NeetoAuth workspaces.

  2. Permission to manage team members/roles in those workspaces.

Install NeetoAuth CLI

macOS / Linux 

brew install neetozone/tap/neetoauth

Shell script: 

curl -fsSL https://neetoauth.com/cli/install.sh | sh

Windows 

irm https://neetoauth.com/cli/install.ps1 | iex

Command Prompt (CMD): 

curl -fsSL https://neetoauth.com/cli/install.cmd -o install.cmd && install.cmd

Verify installation

To verify that you have properly installed NeetoAuth CLI, execute the following command:

neetoauth --help

You should see output similar to:

image_aRwkFRvUm.png

Authenticate your workspace

To get started with NeetoAuth CLI, you first need to authenticate yourself and your workspace. NeetoAuth CLI authenticates with a browser-based login flow and stores credentials locally.

To log into NeetoAuth CLI, execute the following command:

neetoauth login

This prompts you to enter the subdomain for your workspace. If your workspace is acme.neetoauth.com, then enter acme in the prompt.

The command opens a browser window to complete login. After authentication, you should see a success message similar to:

Waiting for authentication.. done!
Logged in as [email protected] on acme.neetoauth.com

Global flags

Every command accepts these persistent flags. All of them are optional:

  • --subdomain <name>: choose which logged-in workspace to target. 
    Required only when you have more than one workspace logged in. 

  • --json: force JSON envelope output

  • --quiet: output raw payload only (or success for message-style actions)

  • --toon: output TOON format (token-optimized output for AI workflows)

Output formats

By default, commands use pretty terminal output.

You can switch output format explicitly using flags:

  • Pretty output (default): table or key-value output with breadcrumbs

  • JSON envelope (--json): includes data and optional metadata

  • Quiet mode (--quiet): raw payload only

  • TOON mode (--toon): compact token-optimized format

For paginated list responses, metadata includes:

  • current_page_number

  • total_pages

  • total_records

Commands quick reference 

Authentication commands

Command

Description

login

Log in to NeetoAuth via browser

logout

Log out and clear saved credentials

whoami

Show current authenticated user(s)

Workspace commands

Command

Description

users

Manage workspace team members. Detailed reference is available here.

products

Inspect products and their available roles. Detailed reference is available here.

Utility commands

Command

Description

doctor

Check CLI health and connectivity

version

Print the CLI version

commands

List all available commands as JSON

setup

Set up NeetoAuth for AI coding assistants

AI assistant setup commands

If you use an AI coding assistant, these setup commands add NeetoAuth CLI guidance to that assistant environment.

Running these commands gives your agent context on how to use NeetoAuth CLI commands, and which output modes to use for each command to keep tool usage token-efficient.

Run the command for the tool you use:

neetoauth setup claude # This will create a new Claude skill that can be added to the Claude code configuration
neetoauth setup cursor
neetoauth setup windsurf
neetoauth setup copilot
neetoauth setup gemini
neetoauth setup codex

You only need to run one (or the ones you actively use). This saves you from manually copying integration instructions into each assistant.

Dealing with multiple workspaces

If you manage more than one NeetoAuth workspace, NeetoAuth CLI helps you manage them much more easily.

You can log into multiple subdomains. If you have already logged into one subdomain, you can log into another by running:

neetoauth login --subdomain globex

When more than one workspace is configured in your CLI, passing --subdomain in commands is mandatory. This ensures commands run against the correct workspace. If you skip it, the CLI returns an error and asks you to specify a subdomain.

Example:

neetoauth users list --subdomain acme
neetoauth users list --subdomain globex

If you skip --subdomain in multi-workspace mode, the CLI returns an error and asks you to specify one.

Troubleshooting with doctor

If something does not work as expected, run:

neetoauth doctor

This checks:

  • Whether you are authenticated

  • Whether the workspace API endpoint is reachable

  • Which CLI version is running

Additional resources

Imagine onboarding a new teammate and setting the right access without jumping across multiple pages in the NeetoAuth UI. You send the invite, choose roles, double-check product permissions, and want to confirm everything is configured correctly.

With NeetoAuth CLI, you can handle that flow from one place: your terminal. You can invite users, assign roles, inspect available product roles, and run a quick health check. When you manage multiple users or multiple workspaces, this command-based flow is easier to repeat than manually going through the same screens every time.

What is NeetoAuth CLI?

NeetoAuth CLI is the command-line interface for managing team members and product roles in your NeetoAuth workspace.

Authentication happens through a browser login flow. After login, the CLI stores your session credentials locally and uses them for subsequent commands.

Why this is useful

Think of NeetoAuth CLI as handling workspace access from one command-driven control panel instead of clicking through multiple screens.

A few examples of what becomes possible:

  • You need to onboard someone quickly, so you invite them and assign their role in one command.

  • You want to confirm product-level permissions before granting access, so you list available roles first.

  • You have to add multiple teammates, so you repeat the same command flow instead of manually redoing UI steps.

  • You want repeatable ops, so you use JSON output in scripts or AI-assisted workflows.

  • You want to do the same set of actions across multiple workspaces you manage, and you can do it with the CLI instead of manually going through the same screens in each workspace.

You do not need to be deeply technical to benefit from this. If you already use simple terminal commands, you will be able to get started with NeetoAuth CLI much more easily, since the commands follow the same patterns you use every day.

What you need to get started

  1. Access to one or more NeetoAuth workspaces.

  2. Permission to manage team members/roles in those workspaces.

Install NeetoAuth CLI

macOS / Linux 

brew install neetozone/tap/neetoauth

Shell script: 

curl -fsSL https://neetoauth.com/cli/install.sh | sh

Windows 

irm https://neetoauth.com/cli/install.ps1 | iex

Command Prompt (CMD): 

curl -fsSL https://neetoauth.com/cli/install.cmd -o install.cmd && install.cmd

Verify installation

To verify that you have properly installed NeetoAuth CLI, execute the following command:

neetoauth --help

You should see output similar to:

image_aRwkFRvUm.png

Authenticate your workspace

To get started with NeetoAuth CLI, you first need to authenticate yourself and your workspace. NeetoAuth CLI authenticates with a browser-based login flow and stores credentials locally.

To log into NeetoAuth CLI, execute the following command:

neetoauth login

This prompts you to enter the subdomain for your workspace. If your workspace is acme.neetoauth.com, then enter acme in the prompt.

The command opens a browser window to complete login. After authentication, you should see a success message similar to:

Waiting for authentication.. done!
Logged in as [email protected] on acme.neetoauth.com

Global flags

Every command accepts these persistent flags. All of them are optional:

  • --subdomain <name>: choose which logged-in workspace to target. 
    Required only when you have more than one workspace logged in. 

  • --json: force JSON envelope output

  • --quiet: output raw payload only (or success for message-style actions)

  • --toon: output TOON format (token-optimized output for AI workflows)

Output formats

By default, commands use pretty terminal output.

You can switch output format explicitly using flags:

  • Pretty output (default): table or key-value output with breadcrumbs

  • JSON envelope (--json): includes data and optional metadata

  • Quiet mode (--quiet): raw payload only

  • TOON mode (--toon): compact token-optimized format

For paginated list responses, metadata includes:

  • current_page_number

  • total_pages

  • total_records

Commands quick reference 

Authentication commands

Command

Description

login

Log in to NeetoAuth via browser

logout

Log out and clear saved credentials

whoami

Show current authenticated user(s)

Workspace commands

Command

Description

users

Manage workspace team members. Detailed reference is available here.

products

Inspect products and their available roles. Detailed reference is available here.

Utility commands

Command

Description

doctor

Check CLI health and connectivity

version

Print the CLI version

commands

List all available commands as JSON

setup

Set up NeetoAuth for AI coding assistants

AI assistant setup commands

If you use an AI coding assistant, these setup commands add NeetoAuth CLI guidance to that assistant environment.

Running these commands gives your agent context on how to use NeetoAuth CLI commands, and which output modes to use for each command to keep tool usage token-efficient.

Run the command for the tool you use:

neetoauth setup claude    # Creates a skill for Claude Code
neetoauth setup cursor    # Creates a skill for Cursor
neetoauth setup windsurf  # Creates a skill for Windsurf
neetoauth setup copilot   # Creates a skill for GitHub Copilot
neetoauth setup gemini    # Creates a skill for Gemini
neetoauth setup codex     # Creates a skill for Codex

You only need to run one (or the ones you actively use). This saves you from manually copying integration instructions into each assistant.

Dealing with multiple workspaces

If you manage more than one NeetoAuth workspace, NeetoAuth CLI helps you manage them much more easily.

You can log into multiple subdomains. If you have already logged into one subdomain, you can log into another by running:

neetoauth login --subdomain globex

When more than one workspace is configured in your CLI, passing --subdomain in commands is mandatory. This ensures commands run against the correct workspace. If you skip it, the CLI returns an error and asks you to specify a subdomain.

Example:

neetoauth users list --subdomain acme
neetoauth users list --subdomain globex

If you skip --subdomain in multi-workspace mode, the CLI returns an error and asks you to specify one.

Troubleshooting with doctor

If something does not work as expected, run:

neetoauth doctor

This checks:

  • Whether you are authenticated

  • Whether the workspace API endpoint is reachable

  • Which CLI version is running

Additional resources

Can't find what you're looking for?