- changed status to resolved
Allow to create and manage more than 1 API key
Issue #210
resolved
When working on multiple (OSS) projects, it might be useful to use one API key per project (or project group) instead of using the same API key everywhere. This way, regenerating the API key wouldn't break all builds but only those which have been using the affected API key.
Comments (1)
-
- Log in to comment
This is already in the system. You can create an organisation and assign your projects to this organisation. Inside of an organisation you can have multiple teams. So you could create a new user, add it to your team and assign the team to the project. That way all users from the team can access/update the project with their own API key.