We have a shiny, new BEE Plugin technical docs site.
You can find a new & updated version of this page here.
You can personalize the way the BEE editor works in your application by configuring BEE Plugin. You can do so using...
- client-side configurations
- server-side configurations
You can find information on client-side configurations here.
In this article, we will focus on server-side configurations.
Please note that - except for the AWS S3 Bucket configuration - all other server-side configurations are only available on premium plans.
Where to find them
To access server-side configurations, log into your BEE Plugin account management portal and select the application (i.e. the instance of the plugin) that you wish to configure.
In the application's details page, locate the area called Application configuration.
Click on Manage roles to manage user roles. For details on this feature, see "How to configure user roles and permissions".
Click on Open configuration to manage the server-side settings listed below.
- Toolbar options: affect the UI of the editor
- Storage options: determine where the File Manager will store & retrieve images
- Content options: define whether certain content elements (e.g. HTML block) are active or inactive
- Service options: define whether additional services (e.g. photo search) are active or inactive
Let's review them one by one.
In the Toolbar Options tab you can:
- control individual settings that affect the top toolbar in the editor
- decide whether to hide the toolbar completely
For example, in our MailUp App for Shopify, we hide the toolbar completely and control the editor (Show preview, Send test, Save) from buttons in the app UI (not in the editor). Here is how it looks.
If you decide to go this route, use the functions listed at the bottom of this page to control the editor from your UI.
Under storage options, you can instruct the Plugin...
- to use your own AWS S3 bucket, instead of ours. See Configuring your own S3 bucket.
- to leverage your own file storage system (e.g. your application already has a place where images and other assets are stored). See detailed information on using your file system.
In this tab you can enable special blocks of content that will be shown in the Content panel inside the editor.
Currently you can enable the custom HTML block, a content module to allows your users to include their own HTML code. See detailed information on using the HTML content block.
The last tab allows you to enable optional services that extends the functionality of the editor.
The services are:
- Photo search: when this is active, a new feature becomes available in the File Manager. It leverages an integration with some popular stock photo services to offer users of the editor the ability to search through large repository of high quality images. The images are free to use under the Creative Commons Zero (CC0) license. See detailed information on the search stock photos feature.
- Row background image: when this is active, advanced users of the editor can set an image as background when editing a row.
- Dynamic images: when this setting is enabled, users of the editor can specify both a static placeholder image and a dynamic image URL when adding an image content block. This allows for scenarios such as personalized birthday cards, countdown timers, dynamic ads, and many other user cases in which an image is built dynamically at the time it is served. More about using dynamic images.
- Display conditions: when enabled, it allows you to pass to the editor an array of conditional statements. These conditional statements are presented in a very friendly way, and allow users of the editor to pick a row and apply a display condition to it, picking it from the array. More about display conditions.