Content-cli Profile creation

Hi gauri.pai11,

You're exactly right. It's a common misconception that platform access automatically translates to tool access. Here's a breakdown:

Celonis uses a role-based access control system. Roles like "Analyst" define what users can do within the Celonis platform's user interface (e.g., creating analyses, exploring data).

The content-cli, however, is a separate tool that interacts with the Celonis platform's API. Using it requires specific permissions to authorize those interactions. These permissions are often different from the ones granted by a user's role within the Celonis application.

That's why, even if the user has the correct API key and team URL, the "The provided team or api key is wrong" error can appear. It's not that the key itself is wrong, but that the user isn't authorized to use that API key with the content-cli.

In essence, analyst permissions within Celonis don't automatically grant access to use the content-cli. The user needs specific permissions to use the CLI and its associated API calls.

Therefore, the best course of action is to:

• Double-check Security Permissions: The user should verify their security permissions within the Celonis platform, specifically those related to API access and the content-cli.

• Contact a Celonis Administrator: If necessary, they should contact their Celonis administrator to request the appropriate permissions. The administrator can grant the user the required access to use the content-cli effectively.