Security, Access Control, and Governance
Security questions center on operators, groups, and named rights. Know the security zones, folder permissions, and the operator/group hierarchy that governs UI and data access. Understand named rights (e.g., admin, workflow execution, delivery management) versus folder-level read/write, and how data filters restrict visible records. Candidates must know password policy, session management, encryption of stored credentials, and audit logging. Governance includes approval workflows, change management, and separation of duties between developers and operators.
Traps: assuming folder permissions override named rights (both apply - most restrictive wins for access); forgetting that security zones can block connections by IP; and misjudging schema access - a group needs rights on both the schema and the folder. Another classic: confusing operator vs. group inheritance and forgetting that admin bypasses many checks.
Rule of thumb: least privilege via groups, not individual operators; scope by folder and zone. Worked example: a regional team should see only their recipients - create a security zone by IP/domain, a group with folder rights to the regional folder, and a data filter on the recipient schema limiting by region, rather than granting admin and relying on training.