Skip to main content

​
What Entity Manager is for

Entity Manager is your operational window into the Context Registry. While entity types and context types are definitions, Entity Manager is where you work with live records — the actual people, businesses, files, and other instances in your workspace. From here you can:
  • Browse instances by entity type.
  • Inspect structured context attached to each record.
  • Add new instances.
  • Enrich records with additional context (manually or with agent assistance).
  • Explore how context types relate to an entity through visual maps.
Screenshot placeholder Entity Manager (/cir/em): left tree of entity types and context types, center records table, optional right detail panel.

​
Open Entity Manager

From Intelligent Registries, choose Entity Manager under the Context group. You can also deep-link to a specific entity type (/cir/em/[entity_type_id]) when working on one category.

​
Layout overview

Entity Manager uses a three-panel layout: Select an entity type in the tree to load its instances. Select a context type to filter records to that shape of data.
Screenshot placeholder Records table with search, pagination, and column headers derived from the active context type schema.

​
Add a new instance

Click Add instance (or the equivalent control for your entity type) to create a new record:
  1. Choose the entity type if not already selected.
  2. Fill in primary context fields — often name, email, or other identity fields.
  3. Save — the instance appears in the table and can be used in Tracks, registry pages, and elsewhere.
Some entity types offer agent-assisted creation: describe the record in natural language and the system maps values into the primary context shape.
Screenshot placeholder Add instance dialog with form fields or agent chat panel for guided entry.
Video placeholder (Screen Studio) GIF: select People entity type → Add instance → fill primary fields → new row appears in table.

​
Add context to an existing instance

Select a row to open entity detail. From there you can add context — attach a new structured slice of information using one of your context types:
  • Type or paste information in a conversational panel (agent extracts fields into the schema).
  • Or enter values directly in a form when manual entry is configured.
Examples: add work history to a contact, attach financial notes to a business, log a timeline event on a file entity.
Screenshot placeholder Add context agent panel or form on entity detail, with context type selector.

​
Context visualization views

Entity detail may offer alternate views of how context connects — graph, map, or timeline-style layouts depending on your workspace configuration. These help you see relationships between context types on one entity without reading raw tables.
Screenshot placeholder Entity context graph or map view showing nodes for different context types on one entity.

​
Entity Manager vs. Contact Book

Contact Book is optimized for day-to-day contact relationship work — search, tags, invite to team, quick context chat. Entity Manager is the registry-native view: same underlying people entity (when configured that way), but oriented toward schema, records, and cross-entity-type administration. Use Contact Book for relationship workflows; use Entity Manager when you need to inspect registry structure, bulk-browse instances, or manage non-contact entity types (files, ideas, assets, etc.).

​
Intelligence Timeline

Every add, update, or enrichment in Entity Manager contributes to the Intelligence Timeline — the per-organization audit trail for that entity. When you hand a record to a teammate or agent, they can read the timeline to see how context accumulated instead of starting from a static snapshot. Next: Intelligence Timeline — full guide to audit trail, verification, and information flow.

​
Connection to Tracks

When you add someone to a track, you pick an instance of the track’s entity type. Instances you create or enrich in Entity Manager are the same records Tracks operate on — keeping context here improves handoffs and agent continuity on track instances. Next: Context operations — saved reads and writes against registry data.