What is a one sentence summary of your feature request?
Improt & Export
Please describe your idea in detail. What is your problem, why do you feel this idea is the best solution, etc.
We request implementation of:
Group Export Feature
Ability to export group configurations (name, description, policies, priorities)
Export formats: CSV / JSON
Group Import Feature
Ability to import groups in bulk
Option to:
Create new groups
Clone existing groups
Apply policies automatically
Policy Cloning / Template Support (Optional but Recommended)
Create reusable templates for standard configurations
Clone existing group settings across multiple groups
How do you currently solve the challenges you have by not having this feature?
Currently, in the Endpoint Protector (EPP) portal (Device Control → Groups), there is no option to import or export group configurations.
Because of this limitation:
We are unable to reuse existing group configurations
Policies cannot be replicated easily
Each time, we must manually create new groups
Policies must be reconfigured from scratch, which is time-consuming and error-prone
Upload any supporting images that you think should be considered in this idea.
Hi,
Thank you for the detailed request — the use case is clear and the operational pain of manually recreating group configurations from scratch is a legitimate one.
That said, I want to be honest about where this sits for us. A group configuration in EPP is considerably more complex than it might appear from the UI — it encompasses device control policies across multiple policy types, membership assignments, monitoring and shadowing settings, content filtering rules, network policies, and more, all of which are tightly connected to each other and to other parts of the system. Building a reliable export and import that handles all of this consistently, including validation on import and graceful handling of conflicts, is a substantial engineering effort — not a simple data dump.
There is also currently no existing import/export infrastructure for this type of configuration data in EPP, which means this would need to be built from the ground up.
For those reasons, this is something we see as a longer-term roadmap item rather than a near-term addition. It’s a valid improvement and we’ve noted it, but we want to be transparent that it competes with a large backlog of other requests and the timeline is not something we can estimate right now.
We’ll keep this thread updated as our roadmap evolves.
