Skip to main content

Disclosures Library

How to use the Disclosures library to find and manage disclosures.

Written by Austin Carroll

The Disclosures Library in Brand Portal is used to store approved disclosure language and manage it throughout its lifecycle, from creation to versioning, expiration, and ongoing updates.

This guide explains how to access the library and perform common tasks.

Access the Disclosures Library

  1. In the left sidebar, open Brand Portal

  2. Select Disclosures

You will see a list of all disclosures in your organization. The tabs at the top of the page also take you to Products and Libraries, the other sections of the Brand Portal.

From this page, you can search, filter, and open individual disclosures.

Find and Filter Disclosures

Use the tools at the top of the Disclosures page to locate specific items.

You can:

  • Search by name or text

  • Filter by attributes such as status, product, channel, geography, or date

  • Click a count in the Needs attention strip (for example, Expiring within, Expired, or Never checked by a scan) to see only those disclosures

  • Browse the full list

Filters help narrow results when managing large disclosure libraries.

Create a New Disclosure

  1. Go to Brand Portal → Disclosures

  2. Click Add Disclosure

  3. Enter the required information, including:

    • Name

    • Disclosure text

    • Severity

    • When to Use (optional description)

    • Required formatting (optional, see below)

    • Metadata such as product, channel, audience, geography, and dates

  4. Click Create Disclosure

Disclosure Text must be the approved wording itself, exactly as it should appear in content. Put any instructions on how to check it in AI Prompt (structured). Warrant won't save disclosure text that reads as checking notes rather than disclosure wording.

New disclosures are Enabled as soon as they are created, so they are used in compliance scans right away. To add many disclosures at once, click Import and upload a spreadsheet or document, or use the Download menu to get a blank template.

Require formatting for a disclosure

Some disclosures must look a certain way, not just say the right words. You can set this when you add a disclosure, or later on its page:

  1. Open the disclosure and click Edit.

  2. In Required formatting, turn on Must be italic or Must be bold as needed, and enter a Minimum font size (pt) if there is one (1 to 72pt).

  3. If only part of the disclosure must be bold, such as each risk name in a risk disclaimer, leave Must be bold off and list those parts under Phrases that must be bold (one per line), using the exact words from the disclosure text.

  4. Click Save formatting.

Outside edit mode, the Required formatting card shows what is required, or No formatting required. Scans flag the disclosure when it appears in content but isn't formatted this way. The requirement applies to the disclosure and all of its approved variants. Formatting is checked from the file in PDFs and documents. In images and scanned pages it is judged from how the page looks, which is less precise. Where formatting can't be read, only the wording is checked. Leave everything off to check wording only.

Formatting isn't recorded in version snapshots, so an older version shows Formatting is not recorded in this version snapshot.

Use placeholders for values that change

Some disclosures include a value that is different each time they are used, such as a date, a rate or a product name. Write that part of the disclosure text as a placeholder in square brackets, for example:

Rates effective as of [DATE]. APY of [X.XX]% is accurate as of the effective date.

What goes inside the brackets is up to you. [ ], [DATE], [X.XX] and [PRODUCT] all work the same way.

When Warrant checks content against a disclosure with placeholders:

  • The disclosure counts as present when the wording outside the brackets appears in the content and each placeholder holds a real value, for example "Rates effective as of 9/1/2026."

  • A placeholder takes a short value, such as a date, a rate, an amount or a product name. Extra sentences or claims written into a placeholder don't count as the disclosure.

  • The wording outside the brackets still has to match. Reworded text, such as "Rates current as of 9/1/2026", is flagged just as it would be for any other disclosure.

  • A placeholder that was never filled in, either still in brackets or holding a stand-in such as TBD, XX/XX/XXXX or ____, is flagged as an unfilled placeholder.

Keep enough fixed wording around your placeholders for the disclosure to be recognizable, and put some wording between two placeholders rather than placing them side by side. A disclosure that is mostly placeholders is hard to recognize, so it may be reported as missing even when it is there.

In Social, a generated post fills a placeholder only with a value it can find in what you gave it, such as your topic, your instructions, or the page or file you generated from. If it can't find one, the draft keeps the placeholder as [ ] for you to fill in before you submit. If a required disclosure couldn't be added to a generated post, Warrant tells you which one when the post is ready, so you can add it yourself.

Import and Export

  • Click Import to add or update many disclosures from a CSV or Excel file, or from a PDF, Word or text document. You choose what happens to duplicates and see a preview before anything is saved.

  • Open the Download menu and choose Download template (XLSX) for a blank template, or Export all disclosures (CSV) to export the disclosures that match your current filters.

  • The template's optional Formatting column sets required formatting, with rules separated by semicolons, for example "italic; min 10pt" or "bold: Equity risk | Interest rate risk". Leave it blank to keep the current setting, or enter "none" to clear it.

Importing is for admins and users whose role includes Manage Brand Portal. For step-by-step instructions and the template columns, including variants, see Import and Export: AI Policies, Products, Disclosures and Libraries.

Edit Disclosure Details or Metadata

To update a disclosure’s information:

  1. Open the disclosure

  2. Click Edit in the top right (disclosures open read-only by default)

  3. Update the text, description, or metadata fields

  4. Changes save automatically. Click Done when you are finished

Metadata can include product, audience, channel, geography, effective dates, and other tags used by your organization. Only admins, or users whose role can manage the Brand Portal, can edit disclosures.

Enable, Disable or Archive a Disclosure

Disclosures do not go through an approval workflow. A disclosure is checked during compliance scans whenever it is Enabled and not Expired or Archived.

  1. Open the disclosure

  2. Click Edit

  3. In the Details panel, use the Status switch to enable or disable the disclosure

  4. To retire a disclosure, click Archive. Click Restore to bring it back

You can also select several disclosures in the list and use the bulk actions to archive, enable or disable them. Only admins can manage disclosure status.

Where a disclosure is checked

A disclosure's Geography and Channel decide which content it is checked on:

  • Geography: a disclosure with one or more states is checked only on content for one of those states. Content with no state set, or set only to United States, is still checked against it, and so is a disclosure with no geography or only United States. This applies to Library scans, social posts, Monitor and Studio. In Studio, each attached file is checked against the disclosures for its own geography.

  • Channel: on social posts, a disclosure is checked only when its channel fits the post (for example, Social Media fits a LinkedIn post). On other content, the channel guides the review but doesn't leave the disclosure out.

To see which disclosures a scan left out and why, open the file's Scan tab, click the Checked: line under the score, and look under Disclosures not checked.

When a scan finds a disclosure missing, the Required Disclosure box on the finding shows your approved wording. If one of the disclosure's variants is tagged for the content's channel, audience or product, that variant is shown.

Create a New Version of a Disclosure

Use versioning to update approved disclosure language while preserving previous versions.

  1. Open the disclosure

  2. Click Edit, then in the Versions tab click New Version

  3. The disclosure enters version editing mode

  4. Update the disclosure text, description, or metadata

  5. Click Save as New Version, optionally add a change summary, and click Create Version

The updated content is saved as a new version within the same disclosure record. Any files using an older version are marked as "Outdated".

Current Version Behavior

When you save a new version:

  • It becomes the current version

  • This version is shown whenever the disclosure is opened

  • Only the current version can be edited further

  • Previous versions remain available for reference. Click one to view it, and Back to Current to return

  • Historical versions are read-only

This preserves a complete audit history while ensuring only the current language is editable.

View Version History

The Versions tab displays all saved versions of the disclosure.

For each version, you can view:

  • Version number

  • Creation date

  • Author

  • Summary information

Older versions can be opened for review but cannot be modified.

Audit Trail

The Activity tab, next to Versions, tracks activity related to the disclosure, including edits, status changes and new versions.

This provides transparency into who made changes and when.

Usage Tracking

The File Usage section shows where the disclosure is being used across assets.

You can:

  • View linked files

  • See status and locations

  • Export usage data with Download CSV

Usage tracking helps assess the impact of updates and identify affected materials.

Attachments

Attachments can be added to a disclosure to store supporting documents or reference files.

Once added, the disclosure becomes part of the organization’s approved repository and will be automatically used during compliance checks while it is Enabled.

Did this answer your question?