Difference between Repository, Project and Workspace Access keys
Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.
In Bitbucket Cloud, you can configure Access Keys at the workspace, project, or repository level. Each grants a different permission level and applies to different scopes described in this article.
Repository-level Access Key
Access keys added at the repository level grate read access to the repository where the key was added. This means that you can only clone or pull the repository using the key, but you won't be able to push any changes. To clone other repositories, you will need to add this key to each one. For detailed instructions on how to set up repository-level access keys, please refer to the Add access keys article.
Project-level Access Key
Access keys added at the project level access grant read access to the project where the key was added. This means you can only clone or pull repositories within that project using the key, but you won't be able to push changes. To learn how to set project-level access keys, please refer to the Add access keys to a project article.
Workspace-level Access Key
Workspace-level access keys grant read and write access. It applies to all the repositories within a workspace. Workspace access keys can be added by going to Workspace Settings > SSH Keys.
When using the workspace access key to push changes to a repository, the author of the commit will be determined by the local git configuration. For more details, see Configure your DCVS username for commits article.