Discussion: How to align Users between self-managed and SaaS?
Problem
The current Organization proposal is not clearly describing what an Organization User is, and how it is different from an Organization Member. It looks like Users as we describe them still differ between self-managed and SaaS. Ultimately, we want parity between self-managed and SaaS. While functionally Users seem equivalent between self-managed and SaaS, on an account level, they are not. Users on self-managed belong to the instance. This means the Admin has control over deleting a User from the system. The Organization Owner would only be able to control removing the user from their Organization, but not the instance.
What is important is that we keep open source contributions to public groups and projects possible and don't require contributors to become Members of these groups and projects.
Example: Turning a group from public to internal on self-managed does not have any consequences for open source contributors because they have to be users of the system via a system account. But on SaaS it would mean they are locked out as soon as a project is made internal.
Proposal
- We incorporate the concept of external Users as it exists on self-managed into SaaS.
- Organization Users are renamed to Organization Members. Until we introduce internal visibility, there will be no noticeable difference for Users in how they perceive access. Non-Members will be able to comment on public issues as they can today, and only Members will be able to contribute to private Projects. Once internal Projects are re-introduced, only Organization Members would be able to access them. Non-Members would be excluded from accessing internal Projects.