Currently, adding an SSH key in Repository / Project > Access keys only offers read-only access to a specific repository or project.

Some users require SSH keys that are specific only to a single repository or to all repositories within a single project, with write access, without granting broader write access at the workspace level.

Security / least‑privilege use case
Some users have strict security and compliance requirements:

• CI/build servers should have read/write access only to repositories in a single project, not to the entire workspace.

• Workspace‑level SSH keys with write access grant access to all repositories in the workspace, increasing the impact if a build server is compromised.

• Using a service/bot user is not desirable because:

• • It requires managing shared credentials and mailboxes.

• • It weakens auditing and accountability (actions not tied to a real user).

• • Their security guidelines discourage non‑personal accounts.

For these users, project‑ or repository‑scoped SSH access keys with write permissions are considered the cleanest and most secure solution.

Feature request
Allow write access for repository and project access keys so CI/build systems and automation can be granted only the minimum required permissions.

Workaround:  use access tokens for repository/project write acecss