Rating-based restrictions and unknown metadata

Rating-based restrictions compare supplied content metadata within the configured rating scheme and unknown-content policy, adding a distinct condition to other library and account access rules.

A rating restriction uses the item’s interpreted rating metadata. It does not inspect every scene and discover its suitability automatically.

The chosen rating system and handling of unknown metadata belong in the policy.

Compare ranks within the intended scheme

Use an original fictional system called LearnBands:

{
  "scheme": "LearnBands",
  "allowedMaximumRank": 1,
  "blockUnknown": true,
  "items": [
    {"id": "A", "rank": 0},
    {"id": "B", "rank": 2},
    {"id": "C", "rank": null}
  ]
}

Under this declared comparison, A passes, B exceeds the threshold and C fails the unknown-content rule.

Item Interpreted rank Block unknown Permit unknown
A 0 Allow Allow
B 2 Deny Deny
C Unknown Deny Allow

Changing blockUnknown to false changes C’s branch. It does not assign C a known low rating.

This is an invented rank model. National and provider rating schemes have their own identifiers and interpretations; their labels should not be compared as one global alphabetical or numeric order.

Unrated is a separate decision

Emby’s parental-control documentation describes a maximum rating and separate options for unrated content.

A threshold alone therefore does not define every unknown case. Missing, unrecognized and incorrectly mapped metadata can produce different inputs to the actual implementation.

An unrated item is not evidence that the content is suitable for every viewer. It says the relevant metadata did not yield a rating under that interpretation.

Metadata correction can change the result

Emby item information includes an OfficialRating property and other content fields such as tags.

If the item was misidentified or its rating is stale, the access result can reflect that wrong metadata while the physical video remains unchanged.

Content ratings develops the provenance and scheme context. A parental limit cannot correct an incorrectly supplied item identity by itself.

Tags and libraries add separate conditions

Emby documents additional tag-based restrictions and library/channel access controls.

A permitted rating does not override a denied library scope. A permitted library does not remove the relevant rating/tag check.

The exact combination belongs to the configured product policy. The simplified rank exercise illustrates one condition rather than proving all routes of a particular server enforce a complete set.

Account selection is part of the boundary

The relevant user must be active for the intended restriction to apply. A shared device’s friendly name is not the account context, and UI filtering is not a substitute for server operation policy.

See Also

References