Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

stuck from a week | cannot connect cli or vs code entitlement issue

asdasd
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
March 15, 2026

─── Access Denied ──────────────────────────────────────────────────────────────────────────────────────────────────────

You don't have permission to access this resource. Please check your entitlements.

https://bscse-team-n39kxqz6.atlassian.net/rovodev

via cli or rovodev vs code, im not able to connect anymore even my payment method is added and jira site is enabled. and everything enabled. 

1 answer

0 votes
Himanshu Tiwary
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
March 16, 2026

Hi @asdasd ,

Welcome to the community!!
This looks like an entitlement/access issue on the Atlassian site, not a CLI or VS Code bug.

For Rovo Dev in the CLI and VS Code/IDE, Atlassian requires that Rovo Dev is enabled for that site and that the user has access to use it. Atlassian’s current docs also show that setup is site-based, not just “payment method added” or “Jira enabled.”

So if you are seeing:

Access Denied You don’t have permission to access this resource. Please check your entitlements.”

the most likely checks are:

  • Rovo Dev is not fully enabled on that specific site
  • your user is not included in the required access/group setup
  • you authenticated against the wrong Atlassian site

or the site has a Rovo Dev activation/entitlement mismatch that Support needs to fix. Community answers for similar errors point to site enablement and user-group access as the first things to verify, ask your site admin to verify that Rovo Dev is activated on that Jira site, that your user has been granted access, and then re-authenticate to the correct site. If all of that is already correct, this should be raised with Atlassian Support as an entitlement issue.

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events