User Roles are permission profiles that control what your users can access and do in Mumara Campaigns. You manage them under Users → User Roles. A role isn't assigned to users directly — it's attached to a package, and users get the role through their assigned package.
When creating a role, you name it and pick permissions from a hierarchical tree: checking a parent category enables all its child permissions, or you can select individual actions independently. A search box helps you find specific permissions, and Check All enables everything at once. Permission categories cover Contact Lists, Contacts (including import/export), Custom Fields, Segmentation, Broadcasts, Drip Campaigns, Split Tests, Triggers, Sending Nodes, Sending Domains, Web Forms, Statistics, Suppression (email, domain, and IP), and Mumara AI — where each AI surface (Broadcast Chat, Builder Chat, Drip Chat, Assistants) has its own permission. Typical role designs range from Read Only (view-only access) through Campaign Manager up to Full Access.
Worth knowing: changes to a role take effect immediately for every user on packages using that role; you can't delete a role while it's attached to a package; AI permissions only work if an administrator has enabled Mumara AI and the license supports it. If a user can't access a feature, check the full chain — permission in the role, role in the package, package on the user — and have them log out and back in if changes don't seem to apply.
