Advanced Permissions
This feature is available on Beefree SDK Superpowers plan and above. If you're on the Core or Essentials plan, upgrade a development application for free to try this and other Superpowers-level features.
Overview
With Advanced permissions, you can tailor permissions for users of your Beefree application by hiding or locking UI elements related to:
content tiles
content settings
layout settings
row & content actions (clone, delete, drag, save)
basically anything in the editor!
These advanced permissions grant total customization of the experience you want to present. Since you set them in the configuration parameters passed to your Beefree app after you’ve initialized it, they could be different each time the editor starts, and have different setups for different users.
Use cases
The absolute flexibility of these permissions makes it easy to address specific needs, not achievable with the Roles and Permissions feature that is available in the Beefree SDK Console.
Create skill-based roles
You can create roles that can act only on a content type. For example, you may want a “copywriter” role for people in an organization that only need to touch copy for editing or translation purposes. To do so, you can:
hide any action that doesn’t involve working on the copy of an email or page.
limit style options for the text itself, by
locking/hiding the side tab;
hiding specific settings in the text toolbar.
Customize image & file management workflows
You can limit how users upload and manage images and files inside the plugin; for example, you want some users – e.g., external collaborators – to select pre-approved images and files uploaded by “admin” users. You can do so by:
disabling drag-and-drop of images onto the stage;
limit actions in the file manager (either the built-in one or your custom file picker) by disabling actions like upload, import, and create a folder.
Another interesting case for using advanced permissions is the possibility to set a maximum size for uploads, per user. The maximum size set per user must not exceed the custom limitation size set on the Activate Custom Limitation on File Manager. The default limit is 20 Mb unless otherwise stated. When this permission is configured, the system will check if a file exceeds the set size before uploading it; if so, the plugin will return an error message, which you may customize using Custom languages.
Create custom, secondary roles
When customers of your applications are structured businesses, typically with a headquarter and a locally-deployed organization (e.g., Real Estate, Travel, Retail), their administrators can create custom, secondary roles to match any internal policy they might have. In this scenario, admins typically want to reduce disruptions of centrally-deployed templates for external communication, while allowing a specific degree of freedom.
Initialize different versions of the editor
By combining multiple permissions, you can load the plugin with radically different experiences, based on the user that starts it. For example:
a “stripped-down” version of the content builder for lower-level subscribers;
a “simplified” version of the builder for new users of an account.
How it works
To set up the advanced permissions, you will need to add the advancedPermissions
object to beeConfig
:
Available permissions and behaviors
You can add all the permissions, some of them, or just one. It is up to your application to create them for all users or a segment, as there are no related server-side settings. You may have a different setup each time the editor starts.
All the permissions use a similar pattern, but the object must match the content schema for the type of content (described in the following section).
Defaults
Each content type below contains a parameter for “behaviors” and “properties”. The behaviors control what someone can, or can’t, do. The properties parameter is an array of sidebar property widgets (e.g., the width slider), and each widget has its default permissions.
Sidebar property widget permissions
All sidebar property widgets (e.g. width slider, alignment, color, etc.) accept the following basic permissions:
Name | Type | Value |
---|---|---|
locked | boolean | true or false |
show | boolean | true or false |
Let’s look at an example of these permissions applied to an image module. The following example will hide the image width property widget and lock the text alignment widget. We’ll cover more of the available settings below.
Default behaviors
All contents and rows (e.g. image module, video module, stage row, etc.) accept the following basic behaviors:
Name | Type | Value | Description |
---|---|---|---|
| boolean | true or false | Can select a row or module to edit its properties |
| boolean | true or false | Can drag and drop the content tile or row onto the stage |
| boolean | true or false | Can view the content in the sidebar |
| boolean | true or false | Can clone a content or row on the stage |
| boolean | true or false | Can drag content to another location on the stage |
| boolean | true or false | Can remove the content or row from the stage |
| boolean | true or false | Can reset mobile style for content properties that make use of it |
Let’s look at an example of these behaviors applied to an image module. The following example will hide the image content tile on the sidebar. We’ll cover more of the available settings below.
Components
filePicker
linktypes
Rows
rows addon
The following code demonstrates how to specify behavior settings for individual row addons. A custom row addon can have its behaviors set independently from the global row settings.
columns
tabs
settings
Content
title
text
image
Parameter | Data Type | Example | Description |
---|---|---|---|
| Boolean | true | Determines whether the |
button
divider
social
dynamic
html
video (email builder block)
form
Icon
You should use the Icon object to set advanced permissions when you need granular control over the display and behavior of icon elements. This allows you to lock certain properties, such as the visibility and font weight, ensuring consistency across different devices and user interactions. Additionally, setting these permissions helps in maintaining a cohesive design by managing how icons respond to mobile and AMP environments.
Icon Configuration Elements
In the given icon code, the structure is defined using objects, properties, and parameters to represent a detailed configuration. The main object, icons
, encompasses two primary properties: behaviors
and properties
, each of which is an object itself. The behaviors
object contains a property canResetMobile
with a boolean parameter set to false
, indicating a specific behavior setting. The properties
object holds various properties such as icons
, fontWeight
, align
, and more, each representing different characteristics and settings for the icons. Each of these properties has parameters assigned to them; for instance, the icons
property has show
and locked
parameters set to true
, determining the visibility and lock status of the icons. This nested structure using objects and properties with defined parameters represent the configuration settings in the code.
Behaviors Object
The table below outlines the configuration elements, their data types, descriptions, and default values for the behaviors object used in the icon configuration.
Configuration Elements | Data Type | Description | Default Value |
---|---|---|---|
canResetMobile | boolean | Indicates whether icons can reset to default settings on mobile devices. | false |
Properties Object
The table below outlines the configuration elements, their data types, descriptions, and default values for the properties object used in the icon configuration.
Configuration Elements | Data Type | Description | Default Value |
---|---|---|---|
| object | ||
| boolean | Determines if the icons are visible. | true |
| boolean | Indicates if the icons' visibility setting is locked. | true |
| object | ||
| boolean | Determines if the font weight option is visible for icons. | true |
| boolean | Indicates if the font weight option is locked. | false |
| object | Aligns icons within their container. | NA |
| object | Sets the font family for icon labels. | NA |
| object | Sets the font size for icon labels. | NA |
| object | Sets the text color for icon labels. | NA |
| object | Sets the size of the icons. | NA |
| object | Sets the spacing between multiple icons. | NA |
| object | Sets the spacing around individual icons. | NA |
| object | Sets the padding around icons. | NA |
| object | Hides icons on mobile devices. | NA |
| object | Hides icons on AMP-format pages. | NA |
| object | Sets a unique identifier for icons. | NA |
| object | Sets the space between letters in icon labels. | NA |
paragraph
list
menu
table
Addon
In this section, we will explore how to assign advanced permissions and behaviors for various addon types, specifically focusing on how to customize permissions for custom addons and row addons. These permissions can override default settings to provide granular control. For instance, an image addon can have specific permissions different from the default image block permissions.
To successfully use this feature, follow these steps:
Identify the Addon ID: Obtain the unique ID of the addon you wish to assign permissions to.
Define Custom Permissions: Based on the type of addon, assign relevant permissions in your configuration file.
Override Default Permissions: Specify advanced permissions for the addon, ensuring they override the default ones if needed.
Set Specific Behaviors: For row addons, include permissions for individual modules like image blocks inside the row addon.
Apply Global Restrictions: Optionally, set global restrictions for all mixed and row content addons for consistent behavior.
By following these steps, you can effectively manage and customize addon permissions.
The following code provides an example of the different content modules and the addons-id
.
The following code shows an example addon with the canViewSidebar
behavior set to true
.
Module inside row addon
The following code defines specific permissions and behaviors for different modules within a row addon.
Add Condition and Edit Condition Buttons
You can choose to display or hide the "Add Condition" and "Edit Condition" buttons when using the Content Dialog with Display Conditions.
The following code shows an example config for how you can display or hide these buttons using advanced permissions.
To hide the buttons, set the CanEditDisplayConditions
and CanSelectDisplayConditions
properties to false
.
Role templates
We’ve put together a few JSON templates of custom roles created with Advanced permissions, so you can get started experimenting with this powerful feature.
You can find them in our GitHub account.
Last updated