Rovo dev Entitlement Check Failed

[arwaz shaikh]

I have recently created an account to try rovodev and on setting up CLI in Mac OS getting this error :

Entitlement Check Failed

 To use Rovo Dev CLI on this organization, enable it in Rovo Dev settings.    │

│                                                                              │

│ https://account.atlassian.net/rovodev       

I have double check Rovo dev CLI is enabled in my account

[Dr Valeri Colon _Connect Centric_]

@arwaz shaikh That message means the org you’re logged into doesn’t have Rovo Dev enabled, even if your personal account shows the feature. Make sure you’re signed in with the same Atlassian org the CLI is targeting (--site-url). If the org has multiple directories, re-auth with acli auth login and try again. If it still fails, an admin needs to enable Rovo Dev at the org level, not just the user level.

[Jorge Cammarota]

Check organizational access**

* Go to: [https://account.atlassian.net/rovodev](https://account.atlassian.net/rovodev)
* Log in using the same Atlassian account you’re using for the CLI.
* Ensure that you’re part of the **organization** where Rovo Dev is enabled — not just a personal account.
* If you’re testing from a personal/free site, Rovo Dev CLI might not be supported yet. In that case, you need to enable it in an organization plan that supports developer tools.

2. **Enable Rovo Dev CLI for your organization**

* In the **Rovo Dev Admin page**, check for a section like **“Entitlements”** or **“Feature Access”**.
* Find **“Rovo Dev CLI”** and toggle it **ON** for your organization or user group.
* You must be an **Atlassian organization admin** to do this. If you’re not, ask your admin to enable it for your account.

3. **Authenticate again in your terminal**

* After enabling access, log out and log back in from your CLI:

```bash
rovo logout
rovo login
```
* This refreshes the authentication token with the updated entitlements.

4. **Verify entitlement manually**

* Run:

```bash
rovo whoami
```
* This should return your organization and confirm that the CLI access is active.
* If it still fails, you may need to clear the local config:

```bash
rm -rf ~/.config/rovo
rovo login
```