Objects
Review and manage business objects and record types such as Tickets, Deals, People, and Companies.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Review and manage business objects and record types such as Tickets, Deals, People, and Companies.
Concepts covered
Step breakdown
- Open ObjectsStart in the Objects section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
Objects is the account data-model surface. The captured screen shows a search field, Create object, and standard objects such as Tickets, Deals, People, and Companies.
This screen explains the structures that CRM records, workflows, Max summaries, and AI agents depend on.
What each control changes
Search records filters object definitions. Create object starts a new business object. Standard badges identify built-in object types. Row menus open object-specific management actions.
Before configuring workflows, confirm the object model represents the real operating system: customers as People and Companies, revenue as Deals, support as Tickets, and custom objects only when the standard model is not enough.
Operational outcome
Objects make customer memory programmable. The better the object model, the easier it is for workflows, agents, and Max to retrieve the right context and update the right record.
Operational playbook
Use Objects as part of the Frontline Admin Objects operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
Best practices
Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
FAQs
What does Objects control?
Review and manage business objects and record types such as Tickets, Deals, People, and Companies.
Who should use this page?
Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.
How should this page fit into onboarding?
Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.
What should I verify before using this in production?
Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.