You don't have permission to create a context. -- when trying to use a GitHub org

Hey, I created a CircleCI account using GitHub, provided access to my organization on the GitHub screen. Then I created an API key for my account and entered it into CircleCI CLI:

circleci setup

Then I ran:

circleci orb init circleci-orb --debug

My steps were:

  1. Yes, walk me through the process.

  2. ? Would you like to perform an automated setup of this orb? Yes, walk me through the process.
  3. ? Are you using GitHub or Bitbucket? GitHub
  4. ? Enter your github username or organization %my org name%
  5. ? Enter the namespace to use for this orb %my namespace%
  6. ? Orb name %my orb name%
  7. ? Automatically set up a publishing context for your orb? Yes, set up a publishing context with my API key.

And then I’ve got the error:

<< result status: 200 OK

<< {“data”:null,“errors”:[{“message”:“Non-nullable field was null.”,“locations”:[{“line”:3,“column”:3}],“path”:[“createContext”],“extensions”:{“arguments”:{“input”:"$input"}}},{“message”:“You don’t have permission to create a context.”,“locations”:[{“line”:3,“column”:3}],“path”:[“createContext”],“extensions”:{“type”:“PERMISSION_DENIED”,“arguments”:{“input”:"$input"}}}]}

Error: Non-nullable field was null.

You don’t have permission to create a context.

What I’m doing wrong? Also, I cannot navigate to name%/contexts, I see the error “Something Unexpected Happened”

Hi @bagipro,

One reason you might see this error is if you are not be an Organization admin. If this is not the case, please open a support ticket and we’ll be happy to help you resolve the issue.

I have the same issue. Now submitted a support ticket.

What did the solution end up being? I am experiencing the same problem now.

Hi @nkranes-frameio! I think you need to be an admin for that organization. If you are an admin and you can’t create a context, you should definitely open a Support Ticket so we can check on it for you.

I am an admin and have opened a support ticket as well. I just thought maybe I could get some more insight here. Ticket #95337


1 Like

I ended up having a Bitbucket account linked (possibly because we use other Atlassian products, but not bitbucket), removed this, cleared cache, all good.