On this page

Jump to any section using the links below

Account fields allow you to store custom information at the account level that applies globally across your entire Hubhus installation. These fields can be used in email templates, booking forms, automation rules, and anywhere else you need account-wide data.

What are account fields

Account fields are custom data fields that exist at the account level, meaning they store single values that apply to your entire organization rather than individual users, campaigns, or leads. Common use cases include tracking vacation periods, feature flags, global announcements, or any other account-wide information.

Accessing account fields

Go to Account → Account fields. You will see a table listing all existing account fields with their Name, Slug, Placeholder, Type, and Value columns.

Creating a new account field

Click the New account field button in the top-right corner. Fill in the following:

• Name: The display name for the field (e.g., "Is it on?", "vacation on", "Vacation off")
• Field type: Choose between Text, Checkbox, or other available types
• Default value: Set the initial value for the field

The system automatically generates a slug based on the name, which is used in placeholders.

Field types

Account fields support different data types:

• Text: Free text input for storing strings, dates, or other text values
• Checkbox: Boolean values (checked or unchecked) for feature flags or yes/no settings

Choose the type that matches the kind of data you want to store.

Using account field placeholders

Each account field has a placeholder that can be used throughout Hubhus in emails, SMS templates, booking forms, and automation. The placeholder format is shown in the Placeholder column and looks like this:

<hh-account.fields slug="field-slug" />

For example, to display a vacation start date in an email sent to all customers, you would use:

<hh-account.fields slug="ferie-fra" />

Or to check if a feature is enabled:

<hh-account.fields slug="is-it-on" />

Editing account field values

To change the value of an account field, click the yellow edit icon next to the field in the table. Update the value and save. The new value is immediately available in all placeholders across all campaigns.

When to use account fields

Use account fields when you need to store information that:

• Applies to your entire organization, not specific users or campaigns
• Should be referenced globally in templates and automation
• Needs to be changed occasionally and reflected everywhere instantly

Examples include office closure dates, global feature toggles, company-wide announcements, or any other centralized data.

Account fields vs other field types

Understanding when to use different field types:

• Account fields: Global data that applies to the entire account
• User fields: Data specific to individual users (vacation dates, employee numbers)
• Campaign fields: Data specific to individual campaigns
• Lead fields: Data specific to individual leads or customers

Choose the appropriate field level based on the scope of the data you need to store.

Editing or deleting account fields

To edit an account field definition, click the yellow edit icon next to the field name. To delete a field, click the red delete icon. Note that deleting a field removes the stored value and breaks any placeholders using that field.

Summary

Account fields provide a flexible way to store global information that applies across your entire Hubhus account. Create fields for vacation periods, feature flags, or other account-wide data, use the generated placeholders in templates and automation, and update values centrally to reflect changes everywhere. This ensures consistent information across all campaigns and customer communications.

? Common searches

custom fields • field setup • data fields • field configuration

? Also known as

data field • custom field • input field

Related articles

Configuring account settings
Creating and managing user fields
Creating and managing user tags
How do I control what users can see and do?