Modules
In short
Parts of the program that are enabled separately — for example the online store, tyre storage or invoice recognition. Status is shown for the company selected at the top.
Why it matters
- Enable only what the workshop needs and keep the menu uncluttered.
- Set up a module (keys, limits) in one place.
Who can
The administrator only.
How to do it
- Enable. In the module block, choose "Applies to" (whole installation or the company) → "Enabled for the whole installation" or "Enabled for the company".
- Settings. Fill in the module fields → "Save settings". Secret fields are not shown after saving: "saved: leave empty".
- Disable. Disabling blocks new operations of the module but keeps history and settings.
- Connections needed. The line "Connect these blocks for full functionality" leads to "Integrations".
Licence
At the top is the "Licence" card: the installation number ("Copy" button: the Engrana supplier needs it to issue the licence), terms, users and orders this month against the limits, and accepted files. Upload the supplier's file with "Upload licence"; the program checks the signature, the installation number and that the file is not older than the one already accepted. Orders per month are customer orders from sales channels and the online shop; counter sales, orders entered by hand and orders between two Engrana installations are not counted.
If the server has the address of the Engrana supplier's admin panel, the bottom of the card shows "Admin panel link". It shows the server key and its fingerprint: the supplier links the key to your card on their side, so compare the fingerprint with them by phone or in person. Once an hour the server reports the program version, the time of the last backup, free disk space, and the number of users and orders per month — no customer data or documents — and receives a new licence if the supplier has issued one. If the admin panel does not answer, the licence and blocks do not change; the reason is shown in the "Last attempt" line.
Common messages
- "Licence not accepted. …" — the file was changed, signed with a different key or damaged: ask the supplier for a new one.
- "The licence was issued for another installation." — give the supplier the installation number from the card.
- "The licence is older than the one already accepted." — upload the newest file.
- "This version of the program has no licence verification key." — you can upload it after an update.
- "not licensed" — the module is enabled by licence: contact your Engrana provider.
- "The secret cannot be decrypted. Enter it again." — the server encryption key changed: enter the module key again.
- "The company has no own setting: the installation-wide setting applies." — this is not an error.
Questions and answers
How do I upload the licence file, and what do the "Trial period" and "Payment not renewed" notices mean? "Modules" → "Upload licence". The "Trial period of the … block until …" notice is shown to the administrator and can be hidden until the end of the session. "Payment not renewed" means the block's payment date has passed and it works until the date shown (grace period); the notice stays until a renewed licence is uploaded. After that, a block with data is view-only.
Why does a module enabled for the whole installation not work in a company? The company's own setting takes precedence over the installation-wide one: if the module is disabled for the company, it is disabled there even when it is enabled for the whole installation. Choose that company in "Applies to" and enable the module for it.
What does an employee see if the module is disabled? The module's history can still be opened, but no new module documents are created: "The “…” module is not enabled for this company. An administrator enables it on the Modules page."
Why won't a module switch on? The module has required fields: "To enable the “…” module, fill in “…”." Fill them in and enable the module again. A module marked "not licensed" cannot be enabled by the administrator: the licence is set by your Engrana provider.
Can a company administrator enable a module for the whole installation? No: the installation-wide setting is changed only by an installation-wide administrator, and a company administrator changes only their company's setting. An administrator of a single branch does not change modules.
Where next
- "Integrations" — data and service providers.