Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

SSH Keys Option Missing from Workspace Settings Edited


I have admin privileges for two Bitbucket workspaces which I did not create.

  • Workspace "A" is an older workspace that is on the Standard plan.
  • Workspace "B" is a newer workspace that is on the Free plan.

When I compare the workspace settings for A and B, I notice that Workspace A is missing several options, including "SSH keys" and "APPS AND FEATURES".


Why can't I add SSH keys to Workspace A? Could this be a permissions issue?


For additional context, I'm asking this question because I believe it may be related to another issue I'm having: I cannot connect Workspace A to my Docker Hub account. Workspace B connects just fine.


Thank you in advance for your help!



I have identified another difference between Workspace A and Workspace B: I cannot create pull requests to Workspace B from any other workspace.

  • YES:   Personal Workspace -> Workspace B
  • YES:   Workspace A -> Workspace B
  • YES:   Workspace A -> Workspace A
  • NO:    Workspace B -> Workspace A
  • NO:    Personal Workspace -> Workspace A

For example:


Note that the repo in Workspace A was forked from Workspace B:



Why can't I create pull requests from my Personal Workspace or Workspace B into Workspace A?



Another clue! In Workspace A, the Pipelines and Deployments pages show the repository creator's user name instead of the workspace name in the repo path:


Is this a bug?
Workspace B shows the workspace name like I would expect.

1 answer

0 votes

I contacted Atlassian support and they clarified the issue for me: 

  • Workspace A is a personal workspace
  • Workspace B is a shared workspace

Unfortunately it is not possible to convert a personal workspace to a shared workspace. Instead, I need to create a new shared workspace and transfer all of my existing repositories from the personal workspace.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

536 views 4 13
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you