License & Compliance Management

BMS DAM replaces flat fields with a license sub-table architecture—multiple license records per asset, with independent renewal, expiry alerts, regional control, and one License Center.

Core Competencies

License & Compliance Management: A Clear "Compliance ID" for Every Asset


BMS DAM replaces flat fields with a license sub-table architecture, attaching multiple license records to each asset, covering commercial image libraries, portrait rights, music, fonts, video stock, model releases, and more. Each license has its own scope and validity period, its own alerts, and its own controls, and flows into the system-level License Center for unified management.

1. License Sub-Table Architecture

Each asset can carry multiple independent license records, each containing the license type, effective regions, validity period, and status. Every record is renewed, alerted, and controlled independently: when one license expires, the system alerts only that record while others are unaffected—operations simply renew the expired record or swap the asset.

License types use a dictionary registration mechanism: new types take effect upon registration, with no database changes and full compatibility with historical data.

(Image: license information under an asset)

2. Precise Regional Control

Each license record sets its own effective regions, supporting market dimensions such as GLOBAL, CN, US, and JP. When an asset enters the publishing workflow, the system matches license status against the target market: content not covered in a region is blocked precisely, while covered regions pass normally. Licenses without regions support "leave blank to follow the asset's global configuration".

3. Expiry Alerts & Automatic Blocking

Expiry alerts: as expiry approaches, owners are notified tier by tier on a preset schedule (e.g., 90, 30, and 7 days), leaving time to renew.

Expiry blocking: after expiry, linked assets are automatically marked "license invalid", and publication and reference are blocked in real time.

Status visualization: the asset detail page shows all license statuses—valid, expiring soon, expired, disabled.

4. Flexible Type Extension

New license types (such as AI-generated content licenses, KOL collaboration licenses, and industry-specific permits) go live through dictionary registration, with no database changes; historical data and new types coexist seamlessly, with no migration required.

5. License Center

The system-level License Center provides a unified entry for license management:

Subjects & scope: licenses are configured by account, user group, or external visitor, with three access levels—read-only, protected, and full access.

Validity & renewal: each license sets its own start and end dates, with single or batch renewal supported.

Revocation & isolation: licenses can be revoked manually; permissions are reclaimed automatically at expiry, and expired files are automatically isolated from access.

Compliance validation: publishing automatically validates asset license scope and copyright terms; failed validation blocks publication.

Change audit & reminders: every license change (operator, time, subject, terms) is fully logged; automatic reminders are sent before copyright expiry, with follow-up notifications if renewal is overdue.

(Image: License Center interface)

Summary

The license sub-table enables record-by-record management, regional control enables market-level pass and block, alerts and blocking handle risks up front, and the License Center provides a unified entry. Every license is traceable, controllable, and auditable.

Frequently Asked Questions (FAQ)

Q: Which license types are supported? Can we add our own?
A: Common types are preset, including commercial image libraries, portrait rights, background music, fonts, video stock, and model releases; enterprises can register new types themselves, with no development or table changes.

Q: How do multiple licenses on one asset work together?
A: Each license takes effect and is controlled independently. At publishing, the system validates all linked licenses together: publication is allowed only when every license type required by the target market is valid; any expired or missing type blocks that market.

Q: What happens to published content after a license expires?
A: The system automatically flags all published content referencing the asset and notifies operations staff, who can renew the license, replace the asset, or take the content down—all actions logged and traceable.

Q: How are historical assets migrated to the license sub-table system?
A: Parallel transition is supported: the original flat license fields and the license sub-table run side by side, migrated in batches; the old fields are closed after completion, with no business impact.

Q: What is the relationship between the License Center and license records on assets?
A: The License Center is the system-level unified entry, handling license configuration, renewal, revocation, and audit; license records on assets are the objects it manages. The two levels work in sync, fully logged.