Skip to content

Commit 2a933e9

Browse files
Sofie Toft Kristensengitbook-bot
authored andcommitted
GITBOOK-5: No subject
1 parent f0bf318 commit 2a933e9

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

13/umbraco-engage/installation/licensing.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,12 @@
1+
---
2+
description: >-
3+
To get the full experience with Umbraco Engage you need to purchase and
4+
install a license. Learn more about how a license work in this article.
5+
---
6+
17
# Licensing
28

3-
Umbraco Engage is a commercial product. You can run Umbraco Engage unrestricted locally without the need for a license. Running Umbraco Engage in the public domain will display a warning banner in the backoffice and will limit the maximum number of orders to 20. To remove these restrictions, you'll need to have a **valid license**.
9+
Umbraco Engage is a commercial product. You can run Umbraco Engage unrestricted locally without the need for a license. Running Umbraco Engage in the public domain will display a warning banner in the backoffice and limit the maximum page views to 1000 per month. To remove these restrictions, you'll need to have a **valid license**.
410

511
## How does it work?
612

@@ -79,7 +85,6 @@ If you are running on a single domain for both your frontend and backend environ
7985

8086
If you have different domains for your frontend and backend, then it's advised that you configure an `UmbracoApplicationUrl` set to your backoffice URL. This helps the licensing engine know which URL should be used for validation checks. Without this configuration setting, the licensing engine will try and work out the domain to validate from the HTTP request object. This can lead to errors when switching between domains.
8187

82-
8388
An `UmbracoApplicationUrl` can be configured in your `appSettings.json` file like so:
8489

8590
```json

0 commit comments

Comments
 (0)