Issue #3526 resolved

Assign SSH keys per project (currently: per user account) (BB-3019)

Jakub Zalewski
created an issue


I enable access to a project on a server, where other people also have access to. The assigned SSH key leaves open access to my other repositories. Current solution is to register another account just to handle this scenario, but IMO it's nonsense to have a separate project owner for every production server. Not only because you have to register, confirm email, assign admin, etc. every time, but because these project don't appear in 'My repositories' (btw, it'd be nice if projects I'm admin of appeared in a more accessible section)

Example solutions: upload SSH keys in project admin panel, not user admin panel leave as it is and add checkboxes with a 'restrict access' option where you select which project would this key give access to

Comments (4)

  1. Erik van Zijst staff
    • changed status to open

    Agree Jakub, this has been on our radar for quite a while (but hasn't gotten much priority). At Atlassian we use the same workaround (which is problematic because it eats into your plan limits).

  2. Dylan Etkin

    This has been fixed for a while.

    You can register deployment keys against a repo which will provide read-only access to the repo without needing an additional user.

  3. Log in to comment