You can save time building portals by reusing content with content blocks.

Before you begin

If you haven’t already, create a content block key and codes.

Using content blocks in a portal is nearly identical to using them in other areas of Slate, like Deliver or decision letters.

Adding content blocks to a portal

Go to Database → Portals. Select an existing portal, or create a new one.

📝 If your content block includes any merge fields, these need to be represented as exports in one of the portal’s queries.

To place the content block in the appropriate place within your portal:

1. Go to the view where you want the content block to appear.

2. Select a Static Content block, or create a new one.

3. Enter the following code in the location you want to display the content block:

   {{EXPORT-NAME | block: "KEY OF CONTENT BLOCK"}}

   where EXPORT-NAME is the name of the export in the portal query, and KEY OF CONTENT BLOCK is the key of the content block that contains the codes to merge into the portal.
   📝 Note: Spaces in your export names are automatically replaced with hyphens.

4. Select Save.

Example: Dynamic staff signature

To dynamically display an assigned staff member’s signature in a portal, the following code uses an export called staff_assigned and a content block key called staff_signature:

{{staff_assigned | block: "staff_signature"}}

The screenshot below shows an example of a static content portal part where the content block containing a staff member’s signature is prefaced with the text “Questions? Contact your admission counselor!”

We impersonate a record and open the portal. The content block merge field displays the content block code that corresponds with the record’s staff_assigned field.

For instance, if a record has a staff assignment of Gonzo Muppet, the content block with Gonzo’s contact information appears as the following: