Frequently Asked Questions
These FAQ entries are based on the documented runtime model, activation architecture, package flow, and customer portal behavior already implemented in the project.
Operators can edit this message to guide customers toward support, activation help, or reseller follow-up.
Yes. This behavior is controlled from admin and can be enabled or disabled without changing templates or controllers.
No. The existing key issuance, signing, validation, and server-linking logic remains authoritative and is reused as-is.
Yes, when the active site profile and the published package rules allow it. This behavior is controlled from Odoo admin and does not require template rewrites.
No. Installation can happen before activation. The website and portal manage package delivery, while activation purchase and lifecycle operations continue through the protected authority routes.
No. The existing key issuance, signing, validation, server-linking, replace, revoke, and reset logic remains authoritative and is reused as-is.
The current product already covers device visibility, application activity, Windows events, file activity visibility, external device usage, alerting, analytical views, and local backup job monitoring.
CharikaControl supports practical USB handling with allow, read-only, or block policies where the monitored endpoint and privileges support enforcement. Operators also keep visibility into observed removable-device usage and transfer context.
Pricing depends on the active admin-managed profile: minimum devices, allowed durations, promotional rules, and range-based discounts are all maintained from Odoo and surfaced on the pricing page.