Documentation

Product guides for ComplyNestly customers and their teams.

Requirements

What requirements are

Why requirements exist, what they change, and what ComplyNestly cannot tell you without them.

A requirement is a statement that a particular employee must hold a particular credential type. It is the standard everything else is measured against.

Without requirements

ComplyNestly can still record credentials and warn you when they expire. It cannot tell you that someone is missing something, because it has no definition of what they should have.

With requirements

  • Each employee gets a requirement status: Ready, Missing Required, Expiring Required, Expired Required, or No Requirements.
  • The Compliance Matrix has columns to render and cells to fill.
  • The Action Center can raise missing required, expired required, and expiring required items.
  • Reports can quantify gaps rather than just list credentials.
  • Renewal Autopilot has a definition of what needs a renewal task.

The three sources

  • Credential Types — the catalog of trackable credentials. Requirements are always expressed in terms of a catalog type.
  • Role Templates — a named set of credential types applied to every employee holding that role.
  • Direct requirements — a credential type attached to one specific employee.

Role-based and direct requirements combine into that employee's effective requirements, which is what the rest of the product reads.

Related guides