@@ -26,7 +26,7 @@ Many features in GitLab can link data together.
A few examples of things that would be disallowed by Organization Isolation are:
1.[Related issues](https://docs.gitlab.com/ee/user/project/issues/related_issues.html): Users would not be able to take an issue in one Project in `Organization A` and relate that issue to another issue in a Project in `Organization B`.
1.[Share a project/group with a group](https://docs.gitlab.com/ee/user/group/manage.html#share-a-group-with-another-group): Users would not be allowed to share a Group or Project in `Organization A` with another Group or Project in `Organization B`.
1.[Share a project/group with a group](https://docs.gitlab.com/user/project/members/sharing_projects_groups/#invite-a-group-to-a-group): Users would not be allowed to share a Group or Project in `Organization A` with another Group or Project in `Organization B`.
1.[System notes](https://docs.gitlab.com/ee/user/project/system_notes.html): Users would not get a system note added to an issue in `Organization A` if it is mentioned in a comment on an issue in `Organization B`.
## Why?
@@ -146,7 +146,7 @@ that might need to cross Organization boundaries and this would solve the proble
This could be an option for a limited set of features and may turn out to be
necessary for some critical workflows.
However, this should not become the default option, because it will ultimately lead to the Cells architecture not achieving the horizontal scaling goals.
Features like [sharing a group with a group](https://docs.gitlab.com/ee/user/group/manage.html#share-a-group-with-another-group) are very tightly connected to some of the worst performing functionality in our
Features like [sharing a group with a group](https://docs.gitlab.com/user/project/members/sharing_projects_groups/#invite-a-group-to-a-group) are very tightly connected to some of the worst performing functionality in our
application with regard to scalability.
We are hoping that by splitting up our databases in Cells we will be able to unlock more scaling headroom and reduce the problems associated with supporting these features.
@@ -245,7 +245,7 @@ Why will GitLab not sign a BAA?
### Data Privacy, Security and the GitLab Data Processing Addendum
1. The [GitLab Privacy Policy](https://about.gitlab.com/privacy/) explains how GitLab collects, uses and shares customers' personal information, and how customers may exercise their rights with respect to that personal information. Additional details on privacy compliance at GitLab, including answers to a number of frequently asked questions concerning GDPR, can be found on the GitLab [Privacy Compliance handbook page](https://about.gitlab.com/privacy/privacy-compliance/).
1. The [GitLab Privacy Policy](https://about.gitlab.com/privacy/) explains how GitLab collects, uses and shares customers' personal information, and how customers may exercise their rights with respect to that personal information. Additional details on privacy compliance at GitLab, including answers to a number of frequently asked questions concerning GDPR, can be found on the GitLab [Privacy Compliance handbook page](https://about.gitlab.com/privacy/#compliance-with-a-legal-obligation).
2. The GitLab Data Processing Addendum, usually referred to as the "DPA", can be accessed from the GitLab [Terms of Use page](https://about.gitlab.com/terms/). As stated in the GitLab Subscription Agreement, the terms of the DPA automatically apply to corporate customers.
3. When asking questions about data privacy, customers may also raise questions about security. Generally, such questions are best directed to the [Field Security Team](/handbook/security/security-assurance/field-security/). However, the following resources may be useful prior to contacting the Field Security team:
@@ -73,7 +73,7 @@ You can send this information to dmca@gitlab.com, you should receive an automate
Disputes regarding namespaces, ownership and trademarks are not governed by DMCA. These disputes must be resolved by the parties involved. GitLab will never act as arbitrators or intermediaries in these disputes and will not take any action without the appropriate legal orders.
For more information, see our [Namespace and Trademark Policy](https://about.gitlab.com/support/gitlab-com-policies/#namespace--trademarks) and [Ownership Dispute Policy](https://about.gitlab.com/support/gitlab-com-policies/#ownership-disputes)
For more information, see our [Namespace and Trademark Policy](https://support.gitlab.com/hc/en-us/articles/11626493890844-GitLab-com-Specific-Support-Policies#namespace-&-trademarks) and [Ownership Dispute Policy](https://support.gitlab.com/hc/en-us/articles/11626493890844-GitLab-com-Specific-Support-Policies#ownership-disputes)
