License Compliance

When a brand's content reaches dozens of global markets, the complexity of compliance management grows exponentially — a single advertisement image may simultaneously involve commercial stock photo licensing, model portrait rights, background music licensing, and font licensing, with each license's validity period and usage scope varying across markets. The traditional approach is to cram this information into several fixed fields, resulting in ever-increasing numbers of fields, increasingly bloated table structures, and persistently coarse-grained management. The Authorization & Compliance Management module in BMS DAM solves this problem fundamentally using a flexible, scalable authorization sub-table architecture.

I. Authorization Sub-Table Architecture: From "Flat Records" to "Structured Governance"

Traditional DAM systems typically record authorization information using flat fields — one row per asset, with several fixed columns storing authorization status. When authorization dimensions expand from "commercial stock photos" to "portrait rights," "music," "fonts," and "video footage," the only option is to keep adding fields, making the table structure increasingly difficult to maintain.

BMS DAM adopts an authorization sub-table design, allowing multiple independent authorization records to be attached under each asset. For example, an advertisement image intended for overseas deployment can simultaneously associate three distinct records: "Commercial Stock Photo License (GLOBAL, expires 2026-12-31)," "Model Portrait Rights (US/JP, expires 2027-06-30)," and "Background Music License (CN, expires 2026-09-15)." Each record can be renewed independently, trigger alerts independently, and control its availability status independently.

This means that when one authorization is about to expire, the system issues a precise alert for that specific record only — rather than broadly flagging the entire asset as "risky." Operations teams can renew or replace that specific authorization without affecting the use of other valid authorizations.

II. Region-Specific Control: Global Content, Local Compliance

The same authorization often entails different compliance requirements across markets. A product image containing human faces may already have portrait rights authorization for the Chinese market, but in Europe, additional data processing consent may be required under GDPR; background music licensed for the Japanese market may be fully covered, while licensing for the U.S. market remains under negotiation.

BMS DAM authorization records support precise regional configuration — from GLOBAL down to specific markets such as CN, US, and JP — with each authorization independently defining its effective scope. When an asset enters the publishing workflow, the system automatically matches the corresponding authorization status based on the target market; content lacking regional authorization coverage is precisely blocked, rather than being either universally approved or universally denied.

For authorizations where regional scope has not yet been explicitly defined, the system supports a flexible handling mode — "region left blank, defaulting to the asset's global configuration" — ensuring no oversight in control while avoiding excessive constraints.

III. Expiration Alerts and Automatic Blocking: From Reactive Response to Proactive Defense

The greatest risk in authorization management is often not "not knowing what to manage," but "forgetting when it expires." The BMS DAM system continuously tracks the validity status of every authorization record:

Near-Term Expiration Alerts:

Automatically triggers notifications before authorization expiration, escalating reminders to relevant stakeholders at preset intervals (e.g., 90 days, 30 days, and 7 days prior to expiration) to ensure sufficient time for renewal processes.

Expiration Blocking:

Upon expiration, the system automatically marks associated assets as "Authorization Invalid" and blocks them in real time during publishing and referencing, preventing expired content from entering the market.

Status Visualization:

The asset detail page clearly displays the current status of all associated authorizations — Valid, Expiring Soon, Expired, or Disabled — enabling operations personnel to grasp the situation at a glance, without manually reviewing contracts one by one.

IV. Flexible Expansion: Adding New Authorization Types with Zero Code Changes

As business grows, so do authorization dimensions. Today you may need to manage commercial stock photos and portrait rights; tomorrow you might add AI-generated content licenses, KOL collaboration licenses, or industry-specific permits.

BMS DAM implements authorization types via an enumerated/dictionary-table registration mechanism. Adding new types requires no database schema modifications — simply register the new value in the system dictionary to activate it immediately. Historical data coexists seamlessly with new types, eliminating the need to migrate legacy data. This design enables authorization management capabilities to evolve continuously alongside business growth, rather than requiring system overhauls for every expansion.

FAQ

Q: Which authorization types are supported? Can I add custom types?

The system includes built-in common types such as Commercial Stock Photos (FLAT), Portrait Rights (PORTRAIT), Background Music (MUSIC), Fonts (FONT), Video Footage (FOOTAGE), and Model Releases (MODEL_RELEASE). Enterprises may register additional types as needed without development effort or database changes — ready to use immediately upon registration.

Q: How do multiple authorizations for the same asset work together?

Each authorization takes effect and is governed independently. During asset publishing, the system comprehensively validates the status of all associated authorizations — the asset is permitted to publish only if all required authorization types for the target market are in "Valid" status; if any type is expired or missing, usage in that market is automatically blocked.

Q: How are already-published contents handled after authorization expires?

After expiration-triggered blocking, the system automatically flags all published content referencing that asset and notifies relevant operations personnel. Teams may choose to renew the authorization, replace the asset, or take down the content — all actions are logged and traceable within the system.

Q: How are historical legacy assets migrated to the new authorization system?

The system supports a "parallel transition" mode — the original flat authorization fields and the new authorization sub-tables operate concurrently. Enterprises can gradually migrate authorization information for legacy assets to the sub-table structure in batches; once migration completes, the old fields are uniformly deactivated — ensuring uninterrupted business continuity throughout the process.