A shared organization is one in which the end-users in said organization have heightened permissions in regards to tickets created in the organization. The options available to this are:
In addition, end-users can also have a heightened permission set that allows them to view all tickets in their organization. For more information on that, see editing_end_users.html.
GitLab Issuesticket field. After doing so, Support-ops will reply to the ticket using the
Support::Support-Ops::Confirm Request for Shared Organization"macro.
Support::Support-Ops::Confirm Request for Shared Organization"macro. They will then note the ticket on the issue and the issue in the ticket. * Once the end-user replies back to the ticket, Support-ops will then apply the changes to the organization or the users, depending on the type of shared organization the end-user desires. * If after a week and there's still no response from the end-user accepting the security risk and choosing the type of shared organization they desire, Suppport-ops will close out the issue in the support-ops-project. In the event the end-user replies after closing out the issue, Support-ops will need to create a new issue and process the request from there.
To change the organization permissions, you will first go to the organization
page. From there, click the text next to the
User field. This will produce a
dropdown. You can then select the option you want.
When selecting "Can view all org tickets", a new line will appear with another dropdown option. You can use this to further modifiy the permissions.
Heightend permissions always increase security risks. This is why GitLab follows the principle of least privilege in everything we do. While the risk is normally minimized by our current processes and procedures, shared organizations do have a slighly higher risk than normal. This is why Support-ops always confirms the end-user understands and accepts this added risk.