Hidden fields (legacy templates)

Overview

This article is for pre-2022 templates, built with our legacy HTML syntax: use it if your tags are in $tag; format. If you use Liquid templates, see Hidden fields (Liquid templates).

Hidden fields don’t appear in the signature block or in MySig. Hidden field data is synced or uploaded into Opensense.

Uses for hidden fields

• A shortened signature block
• Image links, such as headshots
• URL links, such as meeting links
• Badges and awards

Setup

In Designer Studio, find Settings & Fields, and select the Hide box next to the field you want to hide.

Set hidden fields up as conditional fields

Hidden fields should always be set up as conditional fields. At least one field must stay unhidden; most commonly, that’s name.

In this example, the customer uses hidden fields to create a shortened signature block. The hidden data comes from Compliance.

Designer Studio · Every field hidden except name

Signature block and Compliance · Only name in the block; the rest from Compliance

What’s next

• Adding headshots to email signatures
• Conditional fields (legacy templates)
• Syncing users from a CSV file (classic UI)

For further help, contact Opensense Support at help@opensense.com.