Administration
Roles and permissions in Marketing Automation
Each role in Marketing Automation: what it sees, does and cannot do, its approvals, and a permissions matrix.
Applies to Marketing Automation as it works today. Moraph updates the platform continuously, and this page is reviewed when it changes.
On this page
Who can see and do what in Marketing Automation. These roles are the starting point; your administrators set them up to match your teams. Platform roles are assigned in HubSpot as part of the managed service.
Roles
Marketer
Marketing specialist, digital marketing coordinator, campaign manager. Builds campaigns, forms and audiences within the approved templates and rules.
- Sees: Contacts and lists within their team; Templates, campaigns and their review status; Campaign performance reports
- Does: Builds emails from approved templates; Creates audiences from subscribed contacts; Builds forms using approved consent text; Responds to pre-send check and compliance comments
- Cannot: Send a campaign without compliance approval; Change subscription types or consent text; Export contacts unless granted separately
- Approvals: Every campaign they build is approved by a compliance reviewer before it is sent.
- Notified about: Pre-send check results, approvals and returned campaigns.
Compliance reviewer
Marketing compliance officer, compliance analyst, registered principal. Approves or returns marketing content before it reaches customers.
- Sees: Campaigns waiting for review and their pre-send check results; The approval history of every campaign; Templates and their required disclosures
- Does: Approves or returns campaigns with comments; Approves templates and changes to them; Samples sent campaigns for review
- Cannot: Approve a campaign they built themselves; Change platform configuration
- Approvals: Their approval is required before a campaign is sent; template approvals may need a second reviewer under your procedure.
- Notified about: Campaigns waiting for review.
Privacy officer
Privacy officer, data protection officer, chief privacy officer. Decides how consent is captured, which data is used and how data subject requests are handled.
- Sees: Consent and lawful basis records; The list of contact fields synchronized into HubSpot; Data subject requests and their status
- Does: Approves consent text and lawful basis settings; Approves the data fields synchronized into HubSpot; Directs access and deletion requests; Decides on contacts with unknown consent status
- Cannot: Send campaigns; Change configuration outside the change process
- Approvals: Approves consent, data use and data subject request outcomes.
- Notified about: Data subject requests, consent configuration changes and contacts held for a consent decision.
Marketing manager
Head of marketing, marketing director, marketing operations manager. Owns the marketing program and is the day-to-day contact for the service.
- Sees: All campaigns, reports and service reviews; Users and their roles; Change requests and their status
- Does: Schedules approved campaigns; Raises change requests; Requests user additions and removals; Attends the monthly service review
- Cannot: Send a campaign that has not been approved; Grant export rights without privacy officer approval
- Approvals: Configuration changes they request are approved by compliance or privacy where they affect consent, content rules or data use.
- Notified about: Approvals, change status, integration issues and service review packs.
Moraph service engineer
Moraph marketing platform engineer, Moraph service manager. Configures and operates HubSpot for you under approved changes.
- Sees: Configuration, integrations and sending health; Campaigns for pre-send checks; Moraph service portal records for your service
- Does: Runs pre-send checks; Applies approved configuration changes; Monitors and fixes integration and opt-out sync failures; Assesses HubSpot product updates; Runs access reviews and the monthly service review
- Cannot: Approve or send campaigns; Change consent settings or data fields without approval; Export contact data except as directed for a migration or request
- Approvals: Every configuration change needs your approval.
- Notified about: Integration failures, sync failures, complaint levels and vendor notices.
Auditor (read-only)
Internal auditor, compliance tester, examiner (under temporary access). Reviews campaigns, approvals and consent evidence without being able to change anything.
- Sees: Campaigns sent and their approval history; Consent and opt-out reports; Change history and access reviews
- Does: Reads and exports reports within scope, with each export logged; Requests specific evidence through the marketing manager or compliance
- Cannot: Change, approve or send anything
- Approvals: Access is granted by compliance with a scope and an end date.
- Notified about: Nothing by default.
Permissions at a glance
| Action | Marketer | Compliance | Privacy | Mktg manager | Moraph ops | Auditor |
|---|---|---|---|---|---|---|
| Build campaigns and audiences | Own work | – | – | Full | – | – |
| Approve campaign content | – | Approves | – | – | – | – |
| Schedule or send approved campaigns | Own work | – | – | Full | – | – |
| Run pre-send checks | View | View | – | View | Full | – |
| Change subscription types and consent text | – | Approves | Approves | – | Full | – |
| Change synchronized data fields | – | – | Approves | – | Full | – |
| Export contacts | – | – | Approves | Own work | – | – |
| Handle data subject requests | – | – | Approves | – | Full | – |
| Manage users and roles | – | – | – | Approves | Full | – |
| View campaign and consent reports | Own work | View | View | View | View | View |
| View change and approval history | – | View | View | View | View | View |
"Own work" means only records or items assigned to that person; "Approves" means the role signs off the action.
How access is controlled
- No campaign is sent without approval from someone other than the person who built it, and the approval is kept with the campaign.
- Consent text, subscription types and the data fields synchronized into HubSpot are changed only with compliance or privacy approval, through a recorded change request.
- Roles map to HubSpot permissions and teams, configured with you during implementation; exporting contacts is limited to the roles you choose.
- User access is reviewed with your marketing manager on a schedule you set, and auditors receive temporary read-only access with a defined scope and an end date.
Was this page helpful?
Report a problem with this page
Need help with your own setup rather than this page? Raise a support ticket.