Add company rules and custom schema fields

Company compliance rules

A custom rule is a declarative requirement - a field must be present, present in certain conditions, inside a range, or backed by a date within a window - written in the same shape the engine already understands. Unknown keys are rejected at save time, so a typo becomes an error message rather than a rule that silently never fires.

Company rules merge with the pack rules, and your rule wins when it shares an identifier. Findings keep their source, so a reviewer can see at a glance that a requirement came from your organization rather than from a published pack. A rule can be paused instead of deleted when it is temporary.

When to use a rule

Use a company rule for a customer, retailer or internal requirement you must satisfy on top of a regulation. Do not use one to encode a regulation you believe is missing: an unpublished pack should be reviewed and given a version instead, so that everyone can see what changed and when.

Custom schema extensions

An extension adds a field to the passport form for a category: a dotted path key with a type, and optionally an allowed set of values, a pattern, a numeric range and a unit. Reserved path segments are refused so an extension cannot alter the object it is stored in.

Extensions are merged into the category schema for the guided form, enforced whenever a passport is created or updated, and folded into validation as their own findings, so a required custom field is a real requirement rather than decoration. They are plan-limited, which keeps a runaway schema from becoming unmaintainable.

Choosing between them

A field describes what you record; a rule describes when you require it. If you need a new piece of data, add an extension; if you need the platform to insist on existing data, add a rule. Doing both gives you a field that is present, validated and enforced.

Both are scoped to your organization, and both are included when the platform exports a passport or builds a compliance result, so nothing you add lives outside the audit trail.

Screen-by-screen reference

These pages were checked in the organization console on 8 October 2026 using an isolated sample organization. Controls can differ by role, plan, record state and configured providers. Each page below explains its purpose, a practical workflow, the visible controls and what to verify afterward.

Company compliance rules (/settings/rules)

Organization rules express internal or customer requirements beside the selected regulatory pack.

Write an organization rule with a clear code, condition, severity, field, and message that a reviewer can distinguish from official pack findings. Use Form mode for supported checks and Advanced JSON only for definitions the form cannot express. Save, validate a representative passport, and inspect the finding source before applying the rule across a portfolio.

Pause or revise a rule when its requirement changes; validate affected passports again.

Controls and options

• Choose category, severity, message, check and field in Form mode.
• Advanced JSON supports a full rule definition when the form does not cover it.
• More options adds stable code, validity window and note; Add rule stores the definition.
• Inspect the source label of future findings so an organization rule is not mistaken for law.

Custom passport fields (/settings/extensions)

Extensions add typed organization fields to the guided editor, schema validation and scoring.

Create a typed field only after deciding whether it applies to one category or all categories. Choose a stable key and set unit, format, help text, and required status with existing passport data in mind. After saving, reopen an editor to verify the field and rerun validation on affected records instead of assuming old versions were filled automatically.

An extension changes the organization's schema, not the official regulation pack.

Controls and options

• Choose category scope, field key, label and type.
• Set format, unit, help text and required status where the field needs them.
• Use templates as a starting point, then Add extension.
• Reopen a passport editor to confirm the new field appears and validate existing records for gaps.