Custom Fields & Tags

Custom Fields and Tags are the metadata layer that turns HotMic into a true content management system. Just as a CMS uses fields and tags to organize, route, and apply rules to articles or assets, HotMic uses them to organize, route, and apply rules to live streams, recordings, clips, and the creators who produce them.

Together, they give customers the structure needed to operate creator content at scale: filtering it into different surfaces of an app, routing it through workflows, controlling who can produce what, and powering downstream reporting and integrations.

What You Can Do With Fields and Tags

Customers use Custom Fields and Tags throughout HotMic to:

• Filter and surface content — Route streams, recordings, and clips into specific sections of the app (e.g., NBA content into a sports tab, sponsor-branded content into a partner channel).
• Power discovery — Help viewers find content by topic, category, or attribute.
• Apply workflow rules — Trigger different review, approval, or publishing paths in Clip Manager and Stream Manager based on tags or field values.
• Drive routing in webhooks and APIs — Use field values as triggers or filters in Workflows so the right content lands in the right downstream destination.
• Control creator behavior — Restrict the tags a creator can use, or require certain fields to be completed before content can be published.
• Report on creator performance — Group analytics by tag, field value, or creator metadata to understand what's working.

Tags

Every stream, recording, and clip can carry one or more tags. Tags are flexible labels — useful for high-level categorization, topical grouping, and ad-hoc routing.

• Creators apply tags during content creation, or producers/programmers apply them through Clip Manager and Stream Manager.
• Tags are searchable and filterable through the API and the Creator Studio.
• Tags can also be applied to creators themselves, marking them as members of specific teams, programs, or partnerships.

Authorized Tags

Admins can restrict which tags a creator is allowed to apply by configuring authorized tags on the creator's profile. When authorized tags are set, creators can only choose from that list — keeping tagging consistent across an organization and preventing drift.

Custom Fields

Custom Fields are structured metadata defined by the organization. Unlike tags, fields have a defined type, name, and (optionally) a fixed set of allowed values — making them suitable for data customers want to query, report on, or use in business logic.

Field Scopes

Custom Fields can be scoped to either creators or content:

• Creator fields Apply to all of a creator's content. Example: "This user is a contractor from Acme Inc." or "Team: Sports Desk."
• Stream/recording/clip fields Apply to individual pieces of content. Example: "This was an NBA game," "This stream had profanity," "Sponsor: Brand X."

Field Configuration

When admins create a custom field, they configure:

• Field type Creator or content scope.
• Field name The display name shown in the Creator Studio.
• Field label The API label used programmatically (typically the field name without spaces).
• Data type Boolean, Text, Number, Select (single), Multi-select, or Date.
• Field options For Select and Multi-select fields, the available choices.
• Is Required When true, the field must be completed before a creator can end a stream or submit content for publishing.

Where Fields Are Edited

• Creator fields — Managed from the Creators page by clicking Edit on a creator profile.
• Stream / recording / clip fields — Managed by the creator (or a producer) from the content's Custom Fields tab.

How Routing and Rules Work

Tags and field values flow through HotMic's APIs and Webhooks, making them available for routing logic in:

• Customer apps (e.g., display only content tagged as featured on the homepage).
• CMS integrations (e.g., publish only content where sponsor equals a specific brand to a sponsor microsite).
• Workflow automation (e.g., send content with a legal-review field to a separate approval queue).
• Analytics pipelines (e.g., group metrics by tag, team, or campaign).

Because Custom Fields and Tags are exposed through the API, customers can build virtually any routing or rule system on top of them — bringing the flexibility of a CMS metadata model to creator-driven content.