Records
Audience: Admins, Developers, Solution Architects
Purpose: Explains how Records function as the platform’s operational data layer, capturing structured business data and enabling workflows, permissions, reporting, and API-driven integrations.
Overview
Records are the individual instances of business data managed within the platform. They represent the active information that teams create, update, relate, automate, and report on every day. Each Record captures the data values associated with a specific business, such as a deal, asset, policy, or contact. When you interact with your data, you are interacting with Records.
Records power operational execution. They:
Store business data
Participate in workflows and automation
Support relationships between data
Respect permission and access controls
Serve as the foundation for reporting and integrations
While identifiers and required values may vary by Object type, the underlying concept remains consistent: a Record is a single, manageable instance of structured business data.
Records Mastery Checklist
Explore the following topics to understand how Records function within the platform and support operational business data.
Core Knowledge
Record Behavior
Access & Control
Integration & APIs
What’s Next
Continue to Records Core Concepts to establish the foundational mental model required before configuring Records, designing schema strategies, or working with APIs.
Last updated
Was this helpful?