Answers.Body: <p>Technically 3 separate Craft installations would require 3 separate/unique Craft licenses even if they share the same root domain (site.com) and live off in subdomains off of that (a.site.com, b.site.com, c.site.com).</p>
  <p>If any of the sites are using the same <code>config/license.key</code> file, you could delete the duplicates and load the updates page in the control panel. A new one tied to Craft Solo will be generated and you can purchase Craft Pro updates for each individual site.</p>
  <blockquote>
  <p>Not a problem as such, but the same domain for all seems a bit imprecise.</p>
  </blockquote>
  <p>It's a bit ironic in your case because the reason we currently only track the root domain is to let all subdomains of that root domain be able to share a single <code>config/license.key</code> file for a single Craft installation in a multi-site setup.</p>
  <p>Using the notes field in your Craft ID account is probably be best way to keep them sorted.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-17T11:16:35.787Z
Answers.Text: Thanks Brad. The problem I anticipate with “A new one tied to Craft Solo will be generated and you can purchase Craft Pro updates for each individual site” is that I’ve already bought the extra licenses but couldn’t assign them! So it’s good to know you are OK with me using the notes field in my client’s Craft ID account. I'll try the delete/update approach for new ones.
Answers.UserDisplayName: Jonathan Schofield
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-23T18:16:38.280Z
Answers.Text: Just adding that for a new subdomain based clone I tried the delete `config/license.key` and Update to a new license approach, and it worked a treat. Thanks :)
Answers.UserDisplayName: Jonathan Schofield
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-03-16T20:20:30.523Z
Answers.LastActivityDate: 2021-03-16T20:20:30.523Z
Answers.UserDisplayName: Brad Bell
Body: <p>My client has 3 licenses, one for each of 3 subdomains. Let's call them A, B and C.</p>
  <p>C has been derived from B, so has inherited B's <code>license.key</code>. How should I assign the correct license to C? Or does it not matter as long as the appropriate number of licenses have been purchased?</p>
  <p>On a related note, my client's id.craftcms.com log stores the same root domain against all of them, so I have to put a reference to the subdomain in Notes. Not a problem as such, but the same <code>domain</code> for all seems  a bit imprecise.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-02-11T00:53:34.727Z
Comments.Text: Are all 3 of the sites using the same Craft installation? Or are there 3 separate Craft installs?
Comments.UserDisplayName: Brad Bell
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-02-13T18:46:48.877Z
Comments.Text: Hi Brad. 3 separate Craft installs.
Comments.UserDisplayName: Jonathan Schofield
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-03-16T11:55:19.733Z
Comments.Text: Hi @BradBell. Any insights you can offer given my comment above? Everything is working. I just want to make sure I am doing the right thing by way of license admin.
Comments.UserDisplayName: Jonathan Schofield
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2021-03-16T22:11:55.453Z
Comments.Text: Yup, sorry missed this. Added an answer.
Comments.UserDisplayName: Brad Bell
Tags: <license><subdomain>
Title: Assigning the right license to the right subdomain
ThreadText: # Assigning the right license to the right subdomain
  
  (Asked by: username_0 on 2021-02-08)
  
  My client has 3 licenses, one for each of 3 subdomains. Let's call them A, B and C.
  
  C has been derived from B, so has inherited B's `license.key`. How should I assign the correct license to C? Or does it not matter as long as the appropriate number of licenses have been purchased?
  
  On a related note, my client's id.craftcms.com log stores the same root domain against all of them, so I have to put a reference to the subdomain in Notes. Not a problem as such, but the same `domain` for all seems a bit imprecise.
  
  **Tags:** license, subdomain
  
  > **Comments:**
  > **username_1**: Are all 3 of the sites using the same Craft installation? Or are there 3 separate Craft installs?  
  > **username_0**: Hi username_1. 3 separate Craft installs.  
  > **username_0**: Hi @username_1. Any insights you can offer given my comment above? Everything is working. I just want to make sure I am doing the right thing by way of license admin.  
  > **username_1**: Yup, sorry missed this. Added an answer.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-03-16. Score: 2
  
  Technically 3 separate Craft installations would require 3 separate/unique Craft licenses even if they share the same root domain (site.com) and live off in subdomains off of that (a.site.com, b.site.com, c.site.com).
  
  If any of the sites are using the same `config/license.key` file, you could delete the duplicates and load the updates page in the control panel. A new one tied to Craft Solo will be generated and you can purchase Craft Pro updates for each individual site.
  
  > Not a problem as such, but the same domain for all seems a bit imprecise.
  
  It's a bit ironic in your case because the reason we currently only track the root domain is to let all subdomains of that root domain be able to share a single `config/license.key` file for a single Craft installation in a multi-site setup.
  
  Using the notes field in your Craft ID account is probably be best way to keep them sorted.
  
  > **Comments:**
  > **username_0**: Thanks username_1. The problem I anticipate with “A new one tied to Craft Solo will be generated and you can purchase Craft Pro updates for each individual site” is that I’ve already bought the extra licenses but couldn’t assign them! So it’s good to know you are OK with me using the notes field in my client’s Craft ID account. I'll try the delete/update approach for new ones.  
  > **username_0**: Just adding that for a new subdomain based clone I tried the delete `config/license.key` and Update to a new license approach, and it worked a treat. Thanks :)  
  
  ---
  
  