Saved Sep 19, 2026 by @enviglo: First version
+ Everything someone owns from your store is a **license**. Every time someone pays for one of your products, or is given one, Enviglo also keeps a **purchase**. This guide explains how the two work together. It's for store owners and their staff, and it's worth reading before you start giving products away or taking them back.+ ## The short version++ - A **license** is someone owning a product. It always belongs to an Enviglo account, never to a Roblox ID on its own. Your team can revoke it, restore it or move it to someone else.+ - A **purchase** is the record of someone paying for a product, or being given it. It's written once and never changes.+ - One license can have several purchases behind it, such as a subscription that was renewed three times. Each purchase points to the license it made or added to.++ ## Why they're kept apart++ Ownership changes. History shouldn't. When you revoke a license or move it to someone else, the purchases behind it stay exactly as they were: who they were for, what was bought, when, and how. A revoke or a transfer never touches a purchase.++ It's also why sales on Enviglo count paid purchases, not licenses. A product you give away, a code someone redeems or a transfer is never a sale. A renewal or a second copy bought in your game is.++ ## What a purchase records++ Each purchase keeps:++ - the store, the product and the Enviglo account it was for+ - for purchases made in game, the Roblox account that paid, the receipt or game pass, and the Robux spent and the place it was bought in, when your game reported them+ - for subscriptions, how many days of access it added++ You'll find every purchase under **Orders**. See [View purchases](/wiki/purchases).++ ## Where licenses come from++ A license's page shows how its current owner got it under **How they got it**. The **Source** column on the **Licenses** page uses the same words. The license's history starts with how it began.++ | How it happened | How they got it | First history entry |+ | --- | --- | --- |+ | Bought in your game | Bought in game | Bought in game |+ | Given by your team, from the dashboard or Discord | Given | Given by … |+ | Redeemed one of your codes | Given | Redeemed the code … |+ | Added a free product to their library | Given | Claimed for free |+ | Came inside a bundle | Given | Came with a bundle |+ | Came over from myPod | From myPod | Brought over from myPod |++ When a license moves from one person to another, **How they got it** changes to **Transferred**. Its history still starts with how it began, then records each move.++ A bundle hands over the products inside it as well. Someone who gets a bundle gets a license for each product in it that they don't already hold, and more days on any subscription in it that they do. See [Bundles](/wiki/bundles).++ ## What buying again does++ Each product's **How buying works** setting, on its **Pricing** page, decides what happens when someone gets it again. See [Pricing and license types](/wiki/pricing-and-license-types).++ - **One purchase**: one license per person. Buying again while they hold an active license adds nothing, though the payment is still kept as a purchase.+ - **Buy more than once**: every purchase is a license of its own, so one person can hold several licenses for the same product.+ - **Subscription**: every purchase adds the product's days to their license, counted from its current end date if that hasn't passed yet.++ Grants and codes follow the same rules. Granting a one-purchase product to someone who already has it is refused, and a code for it is used up without adding anything.++ Changing **How buying works** doesn't touch licenses customers already hold.++ ## License statuses++ - **Active**: they own it. It's in their library, they can download its files, and games that check with Enviglo can see it.+ - **Revoked**: your store took it back. It leaves their library, their downloads stop, games no longer see it, and the product's Discord role is removed if it has one. The license stays in your records with its history, and you can restore it.+ - **Ran out**: a subscription whose end date has passed. It's still active in your records, but it no longer gives access: downloads stop, games don't see it and the product's Discord role is removed. Owners are told three days before it ends, and again when it does. The customer's page in your dashboard calls this **Expired**.++ ## Revoke, restore and transfer++ - **Revoke** takes the product back, as described above. The purchases behind the license don't change.+ - **Restore** brings the same license back, with its history. Their access comes back with it.+ - **Transfer** moves the license to another Enviglo account. The old owner loses access, and the new owner gets it, along with its downloads and Discord role. The purchases behind it stay as they were, still showing who originally paid.++ Your team does all three from the **Licenses** page. See [Give, revoke, restore and transfer licenses](/wiki/manage-licenses).++ Customers can hand their own licenses to someone else too, if you let them. Tick **Let customers transfer licenses** in your [store settings](/wiki/store-settings), and turn on **Block customer transfers for this product** on a product's **Pricing** page to keep one product out of it. See [Give a license to someone else](/wiki/transfer-a-license) for how it works for customers.++ ## Buying again after a revoke or transfer++ - Paying again in your game makes a **new** license. A revoked license stays revoked, as the record of what happened, and a transferred one stays with its new owner.+ - Owning a game pass isn't a new payment. Registering it again in game doesn't bring back a license that was revoked or given away.+ - A grant or a code after a revoke also makes a new license.+ - A free product can't be claimed again once you've revoked it.+ - A subscription that ran out isn't revoked, so buying it again extends the same license from the day they buy.++ ## How games see licenses++ Your game asks Enviglo about a player by their Roblox ID. Enviglo finds the Enviglo account that Roblox ID is linked to, and answers with that account's licenses that give access right now: active ones, and for subscriptions, ones that haven't run out.++ That has a few consequences:++ - A license only counts in game once its owner has linked the Roblox account they play on. If you give a product to someone by username and they haven't linked Roblox, they own it on Enviglo, but no game can see it until they link. See [Link your Roblox account](/wiki/link-your-roblox-account).+ - For **Buy more than once** products, your game can ask how many copies a player holds.+ - A player banned from your store is reported as banned, and as holding nothing from your store. See [Customers and bans](/wiki/customers-and-bans).++ To set this up in your game, see [Check licenses in your game](/wiki/check-licenses-in-your-game).++ ## Players who haven't joined Enviglo yet++ When someone buys in your game with a Roblox account that isn't linked to anyone on Enviglo, Enviglo makes a placeholder account for that Roblox ID and puts the license on it. Granting or transferring a product to a Roblox ID that isn't linked to anyone does the same.++ - In your dashboard, a placeholder shows up like any other customer, by name and username. It usually carries their Roblox name and picture.+ - When the player links that Roblox account to their own Enviglo account, the placeholder merges into it. Everything on it moves over, licenses and purchases included, and the placeholder goes away.+ - If they already held a license for the same product on their own account, both are kept, side by side.++ ## Licenses and purchases from myPod++ Enviglo is myPod's successor, and myPod's licenses and purchases came with it.++ - Imported licenses show **From myPod** as how the owner got them, and their history starts with **Brought over from myPod**.+ - Imported purchases show as Roblox purchases with a **myPod purchase** reference. Each is linked to the buyer's license for that product when they still hold one. If a myPod license has no purchase linked to it, its page says it came over from myPod, which kept its purchases separately.+ - myPod didn't record what each buyer paid, so a myPod purchase shows the product's Robux price when it was imported.+ - They count as sales, like any other Roblox purchase.+ - myPod buyers who haven't joined Enviglo yet have placeholder accounts too.++ See [Coming from myPod](/wiki/coming-from-mypod) for more on the move.++ ## Keep reading++ - [Give, revoke, restore and transfer licenses](/wiki/manage-licenses)+ - [View purchases](/wiki/purchases)+ - [Customers and bans](/wiki/customers-and-bans)
Everything someone owns from your store is a license. Every time someone pays for one of your products, or is given one, Enviglo also keeps a purchase. This guide explains how the two work together. It's for store owners and their staff, and it's worth reading before you start giving products away or taking them back.
Ownership changes. History shouldn't. When you revoke a license or move it to someone else, the purchases behind it stay exactly as they were: who they were for, what was bought, when, and how. A revoke or a transfer never touches a purchase.
It's also why sales on Enviglo count paid purchases, not licenses. A product you give away, a code someone redeems or a transfer is never a sale. A renewal or a second copy bought in your game is.
Each purchase keeps:
You'll find every purchase under Orders. See View purchases.
A license's page shows how its current owner got it under How they got it. The Source column on the Licenses page uses the same words. The license's history starts with how it began.
| How it happened | How they got it | First history entry |
|---|---|---|
| Bought in your game | Bought in game | Bought in game |
| Given by your team, from the dashboard or Discord | Given | Given by … |
| Redeemed one of your codes | Given | Redeemed the code … |
| Added a free product to their library | Given | Claimed for free |
| Came inside a bundle | Given | Came with a bundle |
| Came over from myPod | From myPod | Brought over from myPod |
When a license moves from one person to another, How they got it changes to Transferred. Its history still starts with how it began, then records each move.
A bundle hands over the products inside it as well. Someone who gets a bundle gets a license for each product in it that they don't already hold, and more days on any subscription in it that they do. See Bundles.
Each product's How buying works setting, on its Pricing page, decides what happens when someone gets it again. See Pricing and license types.
Grants and codes follow the same rules. Granting a one-purchase product to someone who already has it is refused, and a code for it is used up without adding anything.
Changing How buying works doesn't touch licenses customers already hold.
Your team does all three from the Licenses page. See Give, revoke, restore and transfer licenses.
Customers can hand their own licenses to someone else too, if you let them. Tick Let customers transfer licenses in your store settings, and turn on Block customer transfers for this product on a product's Pricing page to keep one product out of it. See Give a license to someone else for how it works for customers.
Your game asks Enviglo about a player by their Roblox ID. Enviglo finds the Enviglo account that Roblox ID is linked to, and answers with that account's licenses that give access right now: active ones, and for subscriptions, ones that haven't run out.
That has a few consequences:
To set this up in your game, see Check licenses in your game.
When someone buys in your game with a Roblox account that isn't linked to anyone on Enviglo, Enviglo makes a placeholder account for that Roblox ID and puts the license on it. Granting or transferring a product to a Roblox ID that isn't linked to anyone does the same.
Enviglo is myPod's successor, and myPod's licenses and purchases came with it.
See Coming from myPod for more on the move.