Skip to main content
An object is a durable business entity represented in Atlas. Examples include a person, organization, account, queue, policy, issue, content item, location, shift, timecard, or interaction. Objects provide stable identity while attributes, relationships, versions, evidence, metrics, access rules, and lifecycle events evolve around them.

​
Object anatomy

An object is composed from a few distinct concerns:
  • Type — the class of thing the record represents.
  • Record — its durable Atlas identity within a workspace.
  • Attributes — typed facts and descriptive state.
  • Identities — keys that connect records to source systems.
  • Relationships — typed links to other records.
  • Governance — access, lifecycle, and audit controls.
Atlas platform artifacts can also participate in the object model. Metrics, insights, dashboards, predictions, decision artifacts, and Lists can be governed and related through the same spine as operational entities.

​
Design rules

Create an object when the concept needs durable identity, relationships, governance, or workflow participation.
Do not derive identity from a display name. Names are attributes; external keys belong in the identity layer.
Avoid creating an object for every event or denormalized warehouse row. Events describe what happened; objects describe what persists.