This workflow is to determine when an account blocked due to violation of our Terms of Use should or should not be re-instated after a user sends a request via Zendesk.
NOTE;
All decisions about account reinstantion are final and there is no process for appeals.
These criteria are to be taken as examples only, and not as binding principles.
If the account violates our ToS again within a 12 month period, it could result in being permanently banned.
An account can be reinstated when;
The content in question has been removed by the Support/Security Team.
The user has given us a substantial reason that they are not violating our Terms of Use.
The user agrees to remove or export the content away from Gitlab.com within 24 hours.
The DMCA/Trademark complaint has been resolved.
An account cannot be reinstated when;
The user refuses to take corrective measures on the account.
The user has been reported on multiple occasions and continues to violate our ToS.
The user intentionally violates our ToS.
Any abusive language or hostile activity towards the support agent.
The account presents damage to the GitLab business and/or brand.
Workflow to Reinstate Account
Support agent, check the admin notes related to the reason for account blocking.
Reach out to the security team on the #security channel in slack to review the account to determine if the account qualifies to have the block to be removed and what corrective measures should be taken by the user to resolve the issues on the account if necessary.
The Security Team will remove the block from the account and restore any projects on the account. All projects will remain private and could be made public again by the user.
Once the Security Team has removed the block and restored the projects, add an admin note to the account detailing that the account has been ublocked.
Notify the user that the restrictions on their account has been removed using Account::Blocked Accounts::Account Reinstated- Success macro.
