Appearance
Your license
Your license is a signed file from Oloom. It sets what this installation may use:
- Modules and features of your offer (for example Business with Field Service),
- Named users: how many active user accounts you can have,
- Term: until when the license is valid,
- Maintenance: until when you are entitled to new versions and support.
The file cannot be edited: Tadbir checks Oloom's signature and rejects a modified file.
Settings > License
Administrators see the status, offer, validity and maintenance dates, licensed modules, named users used and allowed, and the installation ID. Other users only see the status.
| Status | Meaning |
|---|---|
| Valid | Everything licensed is available. |
| Expiring soon | Less than 30 days left. A yellow banner appears at 30 days, a red one at 7 days. |
| Expired or invalid | Licensed modules are unavailable. See After expiry. |
| Missing | No license uploaded yet. Only the core features are available. |
Upload or renew
- Open Settings > License.
- Choose the file from Oloom (at most 64 KB) and upload it.
Tadbir checks the file before saving it. A valid file replaces the previous one immediately, without restarting; a rejected file leaves the current license untouched.
Installation binding. The first license you upload links this installation to its installation ID. Every later file (renewals, extra users) must be issued for the same ID, shown on this page: give it to Oloom when you renew.
After expiry
Nothing is deleted. Users can still sign in, and the core features keep working: users and access, organization settings, files and notifications. Licensed modules (for example CRM, Sales, Field Service) are unavailable until a valid license is uploaded; every user sees a banner, and administrators get a link to upload the new file.
Maintenance and new versions
New versions are included until your maintenance end date. A version released after that date:
- is refused by
upgrade.sh(see Upgrades), - and, if it is installed anyway, locks the licensed modules exactly as an expired license does, with a banner explaining why. Upload a renewed license with a later maintenance date, or go back to the previous version with
rollback.sh.
Server clock
Tadbir remembers the latest date it has seen. If the server clock moves back by more than 24 hours, the license is treated as invalid and a banner asks to correct the clock. Licensed modules come back by themselves once the clock is right. Keep the clock synchronized with your network's time server.
Upload errors
| Message | Cause and fix |
|---|---|
| The license file or signature is invalid. | Wrong or damaged file. Upload the file exactly as received from Oloom. |
| This license belongs to another installation. | The file was issued for a different installation ID. Send Oloom the ID shown in Settings > License. |
| This license has expired. | The file's term is over. Ask Oloom for a renewed file. |
| This license's maintenance ended before this version was released. | Your maintenance does not cover the installed version. Ask Oloom for a renewal, or go back to the previous version. |
| Correct the server clock before installing a license. | See Server clock. |
| The license could not be saved. | The data directory is not writable or is full. Check free disk space under DATA_ROOT. |
Offline and connected licensing
The installation uses offline licensing: the license file is all Tadbir needs, and the server never contacts Oloom. Connected licensing (periodic online check) requires outbound internet access from the server and a different setup; ask Oloom if you need it.
Backups
The license file and its companion license.jwt.state (installation binding and latest date seen) are in DATA_ROOT/license and are included in every backup. Keep them together.