Tags

A tag in BNDRY is a label attached to an entity — an individual, company, or trust — to flag something worth knowing at a glance. Tags appear on the entity record, show up in entity lists, and help your team quickly identify where action is needed without opening every file.

Why tags exist

Compliance work involves tracking patterns across a customer base: which customers have an open screening hit, which need a manual review, which are flagged as high risk. Notes capture detail, but they don't help you find all customers in a given situation at once — and two staff members will phrase the same thing five different ways.

Tags solve that by turning those flags into consistent, structured labels. Instead of free-text observations buried in a notes field, a tag like "PEP match" or "manual review needed" means the same thing every time — straightforward to apply, easy to filter on, and simple to report against.

Key properties

Tags in your tenant come from a catalogue set up by the BNDRY team — only tags in the catalogue can be applied. They are organised into types, so a "Screening" type might include "PEP match," "sanctions hit," and "adverse media hit" as separate tags. Each tag displays with a label and colour on the entity record to help it stand out at a glance.

How tags relate

Tags are applied throughout an entity's lifecycle — automatically when a screening runs or an automation completes, and manually by your team when something needs flagging. Entity lists across BNDRY can be filtered by tag, so if you need to find everyone with a "PEP match unresolved" or "manual review needed" flag, tags are how you get there quickly.