Licensing
Mason is a commercial add-on. This page is about what happens when it cannot confirm a licence — which, deliberately, is very little.
Nothing stops working
An unlicensed Mason does not disable the editor, does not refuse to save, and does not touch what your site shows a visitor. You get a notice. That is the whole of it.
This is a considered position rather than an oversight. The person looking at a publish screen is usually not the person who can do anything about a licence, frequently has no idea what one is, and would simply lose their afternoon. Meanwhile the person who can fix it never sees the message, because they are not the one writing a page that Tuesday. Holding an author's work hostage to get a billing team's attention does not work, and costs the wrong people.
So: your content renders, your authors keep working, and the notice keeps asking.
The notice
Where Mason cannot confirm a licence for the domain, a line appears above the editor and on Mason's control-panel screens. For the first seven days it says how long it has been there:
Mason is not licensed on this domain. Editing continues as normal for 5 more days — add a licence key in the control panel to clear this.
After that it stops counting and settles into:
Mason is not licensed on this domain. Nothing has been disabled and your content is unaffected, but this notice will stay until a licence key is added.
Both are notices. Neither changes what Mason does.
The seven days
The clock starts the first time Mason notices a problem — not when it was installed — and it is reset whenever the licence checks out again.
That matters more for an established site than a new one. A site licensed for two years whose renewal lapses has an installation date long in the past; measured from installation it would get no grace at all, on the afternoon a card expired. Measured this way it gets the same week a new site gets. And because the clock resets on success, a site that lapses, renews, and lapses again next year gets the week each time rather than having spent it years ago.
A new installation gets the same seven days before the wording firms up, which makes for a reasonable trial.
Clearing it
Add your licence key in Settings → General Settings, then load any control-panel page.
That last step is easily missed. ExpressionEngine's licence check runs in your browser, in the control panel, and posts the result back — so a licence added by deploying files or editing the database changes nothing until somebody opens a control-panel page. If you have added a key and the notice has not gone, load a CP page and give it a moment.
Local and development sites
Local and staging hosts never show the notice. Anything ending in .ddev.site, .test, .local
or .localhost, plus localhost and 127.0.0.1, is treated as development.
If your development host is not one of those, add it in system/user/config/config.php:
$config['mason_dev_domains'] = ['staging.example.com'];
That list adds to the built-in one rather than replacing it.
What Mason checks, and what it ignores
Mason asks ExpressionEngine for its own licence status and reacts to exactly two answers: invalid and expired.
Everything else is treated as fine, and that is deliberate, because EE reports more than one kind of thing through the same channel. A missing or expired ExpressionEngine key, a domain mismatch on your EE licence, or simply the news that a newer version of Mason exists all arrive by the same route. None of them means your Mason licence is wrong, so none of them produces this notice.