Support/First Class Modules/CompanyIQ evidence search
/

First Class Modules

CompanyIQ evidence search

Searches approved company records and multimodal sources with citations, and queues only already-authorized records for ingestion.

Runtime key
module.company-iq
Experience
Permission-aware company intelligence
Security
Server-enforced

Use the CompanyIQ renderer in a CompanyIQ solution page when analysts need cited company evidence and bounded source ingestion beside complete managed-record lifecycle workspaces.

Open SaaS AppsPage editorMenus & user typesTemplates
Note

The bundled renderer key is module.company-iq. First-class means BuildWithHQ supplies a native, typed, secured runtime experience inside normal app provisioning and the signed-in user's existing permissions.

What it does

Searches approved company records and multimodal sources with citations, and queues only already-authorized records for ingestion.

Key capabilities

  • Run secured 256-to-1024 two-stage or 1998-dimensional retrieval.
  • Preserve source record, page, element, and visual references.
  • Find only records visible through secured Record Graph search before ingestion.
  • Queue durable extraction and embedding through reviewed AI procedures.
  • Keep opportunity activation in the governed action chain.

Common uses

  • Evidence-backed customer opportunity review.
  • Company document and screenshot discovery.
  • Permission-aware source intake.

How it connects

The renderer uses the existing Records and Record Graph services plus the canonical AI source, document-element, chunk, visual-index, and 256/1024/1998 embedding chain.

Where applicable, its records use the universal RecordId conventions so they can participate in secured relationships, activity history, favorites, dynamic fields, notifications, Inbox attention, and global search without copying the source record.

Security and data boundary

The server derives tenant identity and applies DataRole, location, field, record, source, and CanAiReadRecords policy before retrieval or model context. Search results never grant source access.

  • The authenticated service derives the SaaS app, tenant account, user, DataRole, and location scope; browser identifiers are never authorization proof.
  • The page editor composes React components with validated data bindings. Those bindings call typed runtime APIs, whose application services execute reviewed stored procedures.
  • List, search, detail, relation, activity, favorite, and write operations reapply their required server-side permissions.

Add it to an app

  1. Materialize the reviewed CompanyIQ production solution into an owned disposable or provisioned SaaS.
  2. Add the validated module.company-iq block to a CompanyIQ page through the page editor.
  3. Assign server-enforced DataRoles, locations, and AI-read policy, then exercise denied, empty, cited, visual, and source-revocation paths.
Tip

Treat the renderer as evidence retrieval, not mutation authority; route tasks, opportunities, and external actions through normal permissions and approval policy.

Important

A renderer being bundled in the tenant application does not make its data visible in every app. The server returns only components and records authorized for the current app and signed-in user; unavailable or unauthorized blocks fail closed.

Capability review: 2026-09-14. For exact current technical availability, use the generated API Map and first-class module inventory.