Skip to content
boveDAM
FeaturesPricingBlogDocsDesigners & StudiosBrand OwnersAgencies
Sign inStart free trial
ENES

Brand modules

Custom modules

When and how to add custom modules — including the rationale for not having an inline +Add CTA.

Custom modules extend the standard brand module set with sections specific to your brand system: motion tokens, photography art direction, voice and tone, or any other structured content type. They appear in the portal alongside Logos, Colors, and Typography as first-class cards with their own label and icon.

When to use custom modules

Use a custom module when:

  • Your brand system has structured content that doesn't fit the existing module types (Logos, Colors, Typography, Guidelines).
  • You want a dedicated card in the portal with its own icon and label.
  • The content is stable enough to warrant a persistent module rather than a generic asset section.

For unstable or frequently changing content, a regular library section (with files uploaded as assets) is more appropriate. Modules are designed for structured, named data — not arbitrary file collections.

Why there is no inline +Add CTA

boveDAM does not show a persistent "+Add module" button inline on the portal view. This is a deliberate product decision: the portal content surface is client-facing and should remain clean. Module management is an editor action done from the portal's Settings → Modules panel, not from the live portal UI.

This separation prevents accidental module creation by clients who have been granted edit rights on specific sections.

Adding a custom module

  1. Open the portal and click Settings in the editor toolbar.
  2. Navigate to Modules.
  3. Click Add module.
  4. Choose a module type — select "Custom" for a blank module with free-form content fields.
  5. Enter a label (shown as the card title in the portal).
  6. Optionally choose an icon from the icon set.
  7. Click Create module.

The module appears as a card in the portal at the bottom of the modules list. Drag it in Settings → Brand structure to reorder it relative to other modules.

Custom module content types

A custom module supports the following field types:

  • Rich text — formatted paragraphs, lists, and inline code.
  • Key/value pairs — named tokens with a text value (useful for motion tokens, spacing scales, or custom attributes).
  • External links — labeled URLs pointing to Figma files, Notion pages, or any external resource.
  • File attachment — a single uploaded file (PDF, video, or image) shown as a downloadable card.

See also: Brand structure settings · Brand Guidelines