- 2 Minutes to read
- Print
- DarkLight
Permissions for Content Management
- 2 Minutes to read
- Print
- DarkLight
Mapp Engage uses permissions to grant access to information and functions in the system. There are separate permissions for almost every task in the system. Permissions allow you to control precisely the level of access each system user role in Mapp Engage has to different content management functions.
In the Content Management feature, you work with four basic elements.
Blocks
Frameworks
Email Templates
Email Messages
To separate the layout and content creation, each element has four different permissions:
Use
Create
Edit
Delete
Available Permissions
Name | Permission Number | Description |
---|---|---|
Content Management: Use Frameworks | 2100 | System user can view and use frameworks. |
Content Management: Create Frameworks | 2101 | System user can create frameworks. |
Content Management: Edit Frameworks | 2103 | System user can edit frameworks. |
Content Management: Delete Frameworks | 2103 | System user can delete frameworks. |
Content Management: Use Blocks | 2110 | System user can view and use blocks. |
Content Management: Create Blocks | 2111 | System user can create blocks. |
Content Management: Edit Blocks | 2112 | System user can edit the HTML code of blocks. |
Content Management: Delete Blocks | 2113 | System user can delete blocks from the Mapp Engage system. |
Content Management: Use Email Templates | 2120 | System user can view and use system templates. |
Content Management: Create Email Templates | 2121 | System user can create email templates. |
Content Management: Edit Email Templates | 2122 | System user can edit email templates. |
Content Management: Delete Email Templates | 2123 | System user can delete email templates form the Mapp Engage system. |
Content Management: Use Email Messages | 2130 | System user can view and use email messages. |
Content Management: Create Email Messages | 2131 | System user can create email messages. |
Content Management: Edit Email Messages | 2132 | System user can edit email messages. |
Content Management: Delete Email Messages | 2133 | System user can delete messages from the Mapp Engage system. |
Content Management: Use Forms | 2140 | System user can view and use forms. |
Content Management: Create Forms | 2141 | System user can create forms. |
Content Management: Edit Forms | 2142 | System user can edit forms. |
Content Management: Delete Forms | 2143 | System user can delete forms from the Mapp Engage system. |
Content Management: Assign | 2155 | System user can assign any Content Management object to another system user. |
Content Management: View All | 2156 | System user can see all Content Management items, even those items that are not assigned to them. |
Example
To maintain the basic structure of your content management, you give your web developer all permissions for blocks and frameworks.
To maintain your marketing campaigns, you give your email marketing manager all permissions for email templates and messages. However, you limit the ability of your marketing manager to change the structure of the underlying blocks and frameworks.
To manage the content of your email campaigns, you give all message-related permissions to the system users who create the content. However, you limit the ability of content creators to change your frameworks, blocks, or templates.
To achieve your goals, you assign permissions to each role as follows.
Role | Permissions |
---|---|
Email Developer |
|
Email Marketing Manager |
|
Content Creator |
|