Having trouble with ssh key pull and push access across multiple repos and servers

[Dave Sky]

I'm not sure if I'm doing this right but I'm trying to avoid using a certain user account and password to push/pull/etc on our various test/local servers which have multiple repos spread across them, like so:

Server 1: repo 1 and 2
Server 2: repo 3 and 4
Server 3: repo 5

(where the test servers are duplicates of our local computer servers)

We're all OK generating our own keys for our local computers (since we'd be using our own Bitbucket accounts for them anyways), but on Test and Sandbox, we don't want to use a certain user as that means all developers have to know that user's password.

When I create an ssh key for a server and paste it into a repo's settings in Bitbucket, it works fine but says it has read-only access.

I read I can make a key on my account with read-write access, but pasting that same public id_rsa.pub key value there says it's already being used...

Is what I'm asking even possible? I set the server repo remotes to the SSH clone value git@bitbucket.org:ourcompany/ourrepo.git but of course that seems to only allow me read-only access, and I'm not seeing how to give it full read-write access for our server's public key.

Would we need to create separate users for our server instances, like sandboxuser@ourcompany'.com?

[jredmond]

You can add the key to any individual account, but first you must remove it from any repositories where you've added it.