How does Remote CLI authentication and access work?

Remote CLI supports different authentication methods for different customer and partner workflows. Regardless of the method you use, the CLI applies Remote's role-based access control (RBAC) and does not grant additional permissions.

If you have not installed and configured the CLI, follow the Remote CLI quick start guide before setting up authentication.

Authentication methods

Remote CLI supports:

• OAuth: Opens a browser page where you sign in and approve access. Use this method when you want to work as your own Remote user. Run remotecli login to sign in.
• API token: Supports workflows that authenticate with a Remote API token. Run remotecli login --api-key <API_KEY> to sign in.

Follow the Remote CLI developer documentation to configure the appropriate method. Do not share tokens or include them in screenshots, support requests, or version-controlled files.

How permissions work

Remote CLI uses the permissions assigned to your Remote role. A command can only retrieve or change information that your role already allows you to access.

For example, a user who can approve an expense in Remote may be able to approve it through the CLI. A user without that permission cannot use the CLI to bypass the restriction.

What an Unauthorized error means

An Unauthorized error usually means your current Remote role or authentication credentials do not allow the requested action.

If you see this error:

1. Confirm that you signed in to the intended Remote account.
2. Confirm that you selected the intended company.
3. Check whether your Remote role allows the action.
4. Review the command and authentication requirements in the Remote CLI developer documentation.
5. Contact your Remote administrator if you believe your role needs additional access.

Related articles

• See also: Getting started with Remote CLI
• See also: What can you do with Remote CLI?
• See also: How do you troubleshoot Remote CLI?