Qlik Enterprise Manager (QEM) employs a hierarchical permission structure. Permissions are assigned to users or groups for specific servers (e.g., a Qlik Replicate Server) that are managed by QEM. By default, all tasks ("functions") configured on that server automatically inherit the permissions assigned at the server level. This model simplifies administration by allowing global settings, while also offering the flexibility to override permissions for individual tasks when necessary. The core concept is the inheritance of permissions from a parent object (the server) to child objects (the tasks).

A. Qlik Enterprise Manager has its own independent security model; it does not use the same permission system as Qlik Replicate.

B. Permissions are defined and assigned directly within Qlik Enterprise Manager; there is no function to "transfer rights" from a Replicate instance.

D. QEM's permission model is centralized and distinct; it does not use a combined permission set from both Qlik Replicate and Qlik Compose.

---

1. Qlik Enterprise Manager User Guide, May 2023. In the "Security" chapter, the subsection "Managing server permissions" explicitly states: "By default, all tasks on a server inherit the server permissions. If you want a specific task to have different permissions than the server it is running on, you can override the inherited permissions and set task-specific permissions." This directly confirms the principle of inherited permissions.

2. Qlik Enterprise Manager User Guide, May 2023. The "Managing user permissions" section details the permission levels (Viewer, Operator, Designer, Administrator) that can be assigned. These levels are applied within the QEM framework and are subject to the inheritance model described, demonstrating that QEM has its own permission system, separate from the products it manages.