Overview: In continuity with previous releases that introduced Campaign Drafts and campaigns Commenting & Collaboration capabilities, the new Campaign Approval feature introduces the ability to activate Campaign Approval on any Launcher, assign 3 new roles dedicate to campaign approval (Viewer, Editor and Approver) and track the approval status of your campaigns.
The functionalities included in release do not cover for 100% of the use cases exposed in this Idea and in client interviews. This initial Idea will be closed and a new one has been added for future considerations specific to the "Group Admin" Role which includes:
- View the group(s) and manage members for groups that they're assigned as a Group Admin - For Group Admin to be able to create, edit, delete and share launchers with members of managed Groups - Restrict access to create, edit, delete campaign owned or created by members of their groups - No access to API (Administrator role only) ... Please cast your vote and provide comments here if these are still important features for your team! https://ideas.jeto.io/ideas/JETO-I-27
This feature is getting traction and we're starting to prepare a spec. Based on initial scoping, this new role would also come with an approval workflow. Campaign status was built to support this with a "In Approval" and "Approved" Status. Please check this initial "Campaign Lifecycle Diagram" I prepared to support this.
In this scenario, only an "Approver" would have the right to approve assets and program. Also specific people could be assigned to : - Approve specific elements (Email, Landing Page, Marketo Program, etc.) - Be assigned for approval in a specific sequence Ex: User 1 must approve before user 2, etc
If possible, the role can only view the group and users that they're in. They can approve programs create launchers, however, they should not have the ability to create/invite/delete collaborators or admins.
Campaign Approval has been released in October.
Release notes are available here: http://help.jeto.io/en/articles/3314164-campaign-approval
Overview:
In continuity with previous releases that introduced Campaign Drafts and campaigns Commenting & Collaboration capabilities, the new Campaign Approval feature introduces the ability to activate Campaign Approval on any Launcher, assign 3 new roles dedicate to campaign approval (Viewer, Editor and Approver) and track the approval status of your campaigns.
The functionalities included in release do not cover for 100% of the use cases exposed in this Idea and in client interviews. This initial Idea will be closed and a new one has been added for future considerations specific to the "Group Admin" Role which includes:
- View the group(s) and manage members for groups that they're assigned as a Group Admin
- For Group Admin to be able to create, edit, delete and share launchers with members of managed Groups
- Restrict access to create, edit, delete campaign owned or created by members of their groups
- No access to API (Administrator role only)
...
Please cast your vote and provide comments here if these are still important features for your team! https://ideas.jeto.io/ideas/JETO-I-27
This feature is getting traction and we're starting to prepare a spec.
Based on initial scoping, this new role would also come with an approval workflow.
Campaign status was built to support this with a "In Approval" and "Approved" Status.
Please check this initial "Campaign Lifecycle Diagram" I prepared to support this.
https://drive.google.com/open?id=1CW2MkW8J-XDeaOleL6hz5dG7qpxgsTqb
This document is private for now - please request access if you'd like to review
In this scenario, only an "Approver" would have the right to approve assets and program.
Also specific people could be assigned to :
- Approve specific elements (Email, Landing Page, Marketo Program, etc.)
- Be assigned for approval in a specific sequence Ex: User 1 must approve before user 2, etc
Additional feature to consider: allow approvers/admins to view campaigns submitted by other users.
If possible, the role can only view the group and users that they're in. They can approve programs create launchers, however, they should not have the ability to create/invite/delete collaborators or admins.