Skip to main content
This page summarizes the main entities visible in the product and API flows.

Core entities

EntityPurposeKey fields
SearchOne launched search executionid, type, value, status, created_at, user_id, project_id, team_id, search_metadata
Search Result payloadStored final payload attached to a searchresult.cards[], result.leaked_data, result.breached_accounts[], result.registered_accounts[]
Stream eventIncremental event consumed by the result pagetaskId, moduleId, moduleName, result, timestamp, status
MonitorScheduled monitoring definitionid, user_id, name, type, target, frequency, status
Monitoring AlertAlert emitted by monitor processingid, user_id, monitor_id, severity, message, status, created_at
ProjectInvestigation workspaceid, title, description, content, owner_id, team_id, created_at, updated_at
TeamCollaboration boundaryid, owner_id, name, credit_bank_enabled, credit_bank_balance, use_owner_credits
Team MembershipUser role inside a teamteam_id, user_id, role (owner, admin, editor, viewer)
Team InvitationPending invitation workflowteam_id, email, role, invitation_code, expires_at, accepted_at

Search and module states

Typical status flow:
  • pending
  • running
  • finished
  • error

Visibility rules

A field, tab, or panel is displayed only when all required conditions are met:
  1. The search type supports that view
  2. The plan allows the underlying data source
  3. Matching data is present in returned payloads
  4. The user has not disabled the view in display settings
Missing panel usually means no applicable data was returned, not a rendering issue.

Relationships in practice

One search execution yields multiple module outputs (stream events and/or stored cards).
One search can include cards plus optional leaked, breached, and registered account datasets in its stored result payload.
Teams group projects, and projects can reference saved searches, notes, and attachments.
One monitor can generate many alert records over time, each with its own workflow status.