Help Center

Custom Exposures & Integrations

Define your own exposure types and integrate third-party data — using the same overlay mechanism the standard ones use.

Every compliance program eventually runs into a question the standard lists and overlays don't cover. A sector-specific risk your industry tracks. A vendor-management policy that flags suppliers below a certain certification. A board-level metric your auditor wants to see. Custom exposures let you encode those questions in Altana using the same overlay mechanism the standard exposure types use, so the answers show up wherever the relevant company, facility, or product already appears.

What you can model

A custom exposure attaches one or more attributes to a company, a facility, a geography, or a product. The attributes can take any of a few shapes:

  • Static lists. A simple yes/no membership list — "suppliers on our preferred-vendor list," "facilities certified to a specific standard," "companies our legal team has cleared." Upload the list; Altana flags every match and keeps the membership current as you update the list.
  • Scored attributes. A numeric value attached to each entity, with the score's meaning interpreted by the rules you set. A vendor-management score, a sourcing-region risk rating, a supplier-tier classification. Scores can come from your team or from a feed.
  • Time-bound flags. An attribute with a start and end date — a temporary moratorium on a sourcing region, a temporary certification, a known-issue window. Time-bound flags expire automatically and reappear in audit log history.
  • Geographic boundaries. A geofence you define around an area your business cares about — a controlled sourcing region, a customer-defined exclusion zone, a sensitive-operations boundary.

Integrating third-party data

Most custom exposures pull from data your business already has — an internal vendor system, a sector-specific subscription, a research provider, an audit-tracking tool. Altana integrates these through:

  • List uploads. For static lists and one-off cohorts, you can upload a list of identifiers (company names, IDs, addresses) and Altana resolves them to canonical companies and facilities in the graph.
  • SFTP and webhook feeds. For recurring data — scored attributes that refresh on a cadence, time-bound flags that change daily — an administrator configures a feed in Settings and Altana ingests new values automatically.
  • Third-party data partners. For curated risk data that other vendors specialize in — sanctions monitoring, ESG indicators, credit data, news feeds — Altana ships a set of supported integrations. New providers are added on the same overlay scaffold without per-customer development.

Every integrated value lands in Altana the same way: as an attribute on a canonical company, facility, geography, or product, with a source name, a load date, and any associated value or confidence. The source name is part of the exposure record so an auditor can always trace the flag back to where it came from.

Naming and category placement

A custom exposure carries a name and a category placement you choose. The category controls where the exposure sits in lenses and queues — you can drop a new exposure into one of the standard categories (forced labor, financial sanctions, export controls, etc.) or create a custom category alongside them. Custom categories show up in the same filters and the same status workflow as the standard set.

How you'll see this in Altana

  • Custom exposures are configured in Settings: an administrator names the exposure, sets its category, chooses its data source (upload, feed, or third-party integration), and decides whether it attaches to companies, facilities, geographies, or products.
  • Once configured, the custom exposure surfaces on every relevant entity profile, in every workflow that reads from the graph, the same way standard exposures do.
  • Reviewers move custom exposures through the same status workflow as standard ones: Unassessed → In review → Of concern → Cleared.
  • The audit log captures every load, every status transition, and every reviewer action, so the provenance of a custom flag is as defensible as a regulatory list match.

Key terms

Custom exposure
An exposure type you define yourself, encoded as one or more attributes attached to companies, facilities, geographies, or products via the overlay mechanism.
Static list
A simple yes/no membership list you upload. Altana resolves the entries to canonical entities and flags matches across the graph.
Scored attribute
A numeric value attached to entities, with meaning interpreted by rules you set. Can be sourced from your team or from a feed.
Time-bound flag
An attribute with a start and end date. Expires automatically and stays visible in the audit log after expiration.
Third-party data feed
An integration that brings recurring values from an external data provider into Altana as overlay attributes — via SFTP, webhook, or a supported partner integration.
Custom category
A category placement you create alongside the standard exposure categories, so a custom exposure type can have its own grouping in lenses, filters, and queues.
Provenance
The captured source, load date, and reviewer history for every overlay value. What makes a custom flag defensible to an auditor.

Related concepts