<commit_before>---
layout: markdown_page
title: "Licenses"
---

## How is a license created?

[Reference](https://dev.gitlab.org/gitlab/license-app/merge_requests/6)

1. License-app

1. Sales pulls [subscription id](https://license.gitlab.com/subscriptions) from Recurly and presses awesome green button 

1. If customer did not receive [license email](https://license.gitlab.com/licenses), choose customer, and re-send email

## EE access

All access to the Enterprise Edition is offered only along with the [terms](https://about.gitlab.com/terms/), either with a subscription, or an evaluation.

## Evaluation/Trial access rules

1. Small opportunity (small organization and less than 1 standard pack/10 basic packs): Trial is not available. [Send template email](https://docs.google.com/document/d/12X6Cvjwe_jvFi41gvXMLlq91lDgh5oSrRFdQEuEwhl8/edit)

1. Large opportunity (large organization or more than 1 standard pack/10 basic packs): 45 day trials are available and can be extended if needed. Prospect should sign the [Evaluation Agreement](https://docs.google.com/document/d/1YvYWlou1OUsQTEhwYZzj8WXPv9bwPhlcVnLI2euA7EQ/edit?usp=sharing). Print Google Doc as PDF and send to prospect. Signed copies should be saved in Drive with file name as exampleco_eval_agreement_signed032615. End of trial is listed in “Renewal date” of the sales sheet. Sales follows-up until a firm response (yes/no). If answer is no, then access is removed, and customer is informed to remove GitLab Enterprise Edition from their server

1. For users that already have access: sales follows-up until firm response

## Who gets access to EE?

1. Access is granted if user requests it

1. Support handles access

1. If recurly - user told about access through automatic e-mail

1. If bank - sales sends the following [template text](https://docs.google.com/document/d/12X6Cvjwe_jvFi41gvXMLlq91lDgh5oSrRFdQEuEwhl8/edit) via e-mail

## Giving access to EE

1. Recurly subscribers receive automatic message telling them to contact support for access to EE

1. If customer was not informed already, send email about [information to get access](https://docs.google.com/document/d/1xholewfn3PrzdRIFrxCE-0hQdQdryXuBnlUYGmm76iA/edit#heading=h.95yak5j1r9m2)

1. Go to gitlab.com > Subscribers / GitLab Enterprise Edition > Settings > Members> New Project member and add respective username

1. Give access “Developer”

1. Add user to the sales sheet, so we can see which company they belong to

1. Send e-mail to inform the user

## Giving access to the standard subscribers documentation

1. Gitlab.com > groups > Standard > Members > Add members

1. Give access “Developer”

1. Send email to inform the user

## Removing access from EE<commit_msg>fixed info to get access link<commit_after>---
layout: markdown_page
title: "Licenses"
---

## How is a license created?

[Reference](https://dev.gitlab.org/gitlab/license-app/merge_requests/6)

1. License-app

1. Sales pulls [subscription id](https://license.gitlab.com/subscriptions) from Recurly and presses awesome green button 

1. If customer did not receive [license email](https://license.gitlab.com/licenses), choose customer, and re-send email

## EE access

All access to the Enterprise Edition is offered only along with the [terms](https://about.gitlab.com/terms/), either with a subscription, or an evaluation.

## Evaluation/Trial access rules

1. Small opportunity (small organization and less than 1 standard pack/10 basic packs): Trial is not available. [Send template email](https://docs.google.com/document/d/12X6Cvjwe_jvFi41gvXMLlq91lDgh5oSrRFdQEuEwhl8/edit)

1. Large opportunity (large organization or more than 1 standard pack/10 basic packs): 45 day trials are available and can be extended if needed. Prospect should sign the [Evaluation Agreement](https://docs.google.com/document/d/1YvYWlou1OUsQTEhwYZzj8WXPv9bwPhlcVnLI2euA7EQ/edit?usp=sharing). Print Google Doc as PDF and send to prospect. Signed copies should be saved in Drive with file name as exampleco_eval_agreement_signed032615. End of trial is listed in “Renewal date” of the sales sheet. Sales follows-up until a firm response (yes/no). If answer is no, then access is removed, and customer is informed to remove GitLab Enterprise Edition from their server

1. For users that already have access: sales follows-up until firm response

## Who gets access to EE?

1. Access is granted if user requests it

1. Support handles access

1. If recurly - user told about access through automatic e-mail

1. If bank - sales sends the following [template text](https://docs.google.com/document/d/12X6Cvjwe_jvFi41gvXMLlq91lDgh5oSrRFdQEuEwhl8/edit) via e-mail

## Giving access to EE

1. Recurly subscribers receive automatic message telling them to contact support for access to EE

1. If customer was not informed already, send email about [information to get access](https://docs.google.com/document/d/12X6Cvjwe_jvFi41gvXMLlq91lDgh5oSrRFdQEuEwhl8/edit)

1. Go to gitlab.com > Subscribers / GitLab Enterprise Edition > Settings > Members> New Project member and add respective username

1. Give access “Developer”

1. Add user to the sales sheet, so we can see which company they belong to

1. Send e-mail to inform the user

## Giving access to the standard subscribers documentation

1. Gitlab.com > groups > Standard > Members > Add members

1. Give access “Developer”

1. Send email to inform the user

## Removing access from EE
{'fraction_non_alphanumeric': 0.07512428650340637, 'fraction_numerical': 0.02504142883446879, 'mean_word_length': 4.6, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 19, 'https://': 16, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2222368', 'n_tokens_mistral': 1705, 'n_tokens_neox': 1594, 'n_words': 662}