Administration, Security, and Access Management
Access control model
Users are operators; permissions come from security groups and, in Campaign Standard, from Adobe Admin Console product profiles and organizational units. Rights can be granted on folders (read, write, delete) and on schemas or entities, with levels such as all or own. Named rights cover specific capabilities: workflow execution, delivery management, import and export. Technical accounts are separate from human operators and are used by APIs and integrations. Audit trails record changes to schemas, deliveries and security settings.
Traps
- Group membership is additive; removing a user from one group may not remove inherited rights.
- Organizational units filter data visibility; a user can have write rights and still not see a record.
- Admin is not the same as all folder rights; system administration is a distinct profile.
- Technical account credentials are not operator logins and cannot browse the UI.
- Folder permissions do not grant schema permissions, and vice versa.
- Deleting a group can orphan permissions; deactivate instead.
Rule of thumb
Apply least privilege by role: a campaign manager gets folder write on campaigns and delivery execution, not schema design. Test with a non-admin account because admins bypass many checks.
Worked example: A regional team should only see their recipients. Put them in a group with an organizational unit restricted to their region, grant read/write on the regional folder, and give the workflow execution named right only if they own workflows. Verify by logging in as a test operator and opening a delivery from another region - it should be absent, not just read-only.