I'm trying to lean into repoFlow at home, and model some slightly better patterns than open borders to artifacts across all my services. As I'm getting repoflow going I see that I can make users in the console, but then I do have to invite users to workspaces with a manually generate invite link.
The workspaces an abstraction layer, and in each workspace can be many kinds of repositories. For my purposes I'll probably have 2 workspaces, even though 1 would almost certainly suffice.
There doesn't seem to be a way to add a user to a workspace from the admin setting so for a while I was pretty confused why I couldn't add my robot user to a docker repository in my main workspace...
After generating the invite link and accepting though then I see in the workspace settings a simple click to give the robot user access to all repos (if you want)
Can manage allows the user to mutate tags (ie. push latest docker tags). If
the user only has Can deploy then they can only create new artifacts (ie. not
mutate any tags)