Object reports

Object reports covers reports scoped to one dynamic object, using that object’s fields, filters, relationships, pipelines, and record history. Use this page when you are setting up the product surface, reviewing a rollout, or troubleshooting why users see a different result from an administrator.

What this surface is

• Primary purpose: reports scoped to one dynamic object, using that object’s fields, filters, relationships, pipelines, and record history.
• Where users start: Object reports live at /settings/objects/:objectId/reports/list.
• Where administrators configure it: Report studio routes include /settings/objects/:objectId/reports/studio and /settings/objects/:objectId/reports/:reportId/studio.
• Runtime/detail surface: Object reports help teams analyse records without leaving the object configuration boundary.
• Platform connections: Object reports connect object schema, pipelines, relationships, reports, charts, dashboards, exports, and permissions.

Where it lives

Area	Path or surface	Use it for
User surface	Object reports live at /settings/objects/:objectId/reports/list.	Day-to-day work and review.
Configuration	Report studio routes include /settings/objects/:objectId/reports/studio and /settings/objects/:objectId/reports/:reportId/studio.	Setup, permissions, routing, labels, and behaviour.
Runtime/detail	Object reports help teams analyse records without leaving the object configuration boundary.	Testing the live experience users actually see.

Configure it

1. Confirm the audience for this surface and whether they are staff users, portal users, customers, public visitors, or administrators.
2. Open the owning product route: Object reports live at /settings/objects/:objectId/reports/list.
3. Review the configuration route and permissions before changing live behaviour: Report studio routes include /settings/objects/:objectId/reports/studio and /settings/objects/:objectId/reports/:reportId/studio.
4. Define the primary records, fields, statuses, owners, and notifications involved in this workflow.
5. Configure List report, Summary report, and Pipeline report first because they shape the rest of the rollout.
6. Add Relationship report and Parameterized report only after the core path works with sample data.
7. Test the runtime surface as a restricted user, not only as a superadmin: Object reports help teams analyse records without leaving the object configuration boundary.
8. Check downstream connections after saving: Object reports connect object schema, pipelines, relationships, reports, charts, dashboards, exports, and permissions.
9. Record the owner, rollout date, and support path for the configuration.
10. Review the first week of activity and remove any option that users do not understand or need.

Configuration options

Option	Use when	Notes
List report	Users need detailed rows	Keep columns relevant.
Summary report	Users need counts or totals	Group by status, stage, owner, or date.
Pipeline report	Stage ageing or conversion matters	Use pipeline fields and history.
Relationship report	Parent or linked data matters	Verify relationship path.
Parameterized report	Users choose date/team/stage	Keep parameters simple.
Export report	Offline analysis is needed	Check sensitive fields.

Operating notes

• Keep labels aligned with the words users see in the product, especially List report and Summary report.
• Permissions still matter even when a menu, page, or link is visible.
• If users see empty data, check role filters, enabled apps, ownership rules, and saved filters before editing records.
• If a change affects customers or public visitors, test from a logged-out or customer account as appropriate.
• Use reports or logs to confirm the change produced the expected operational result.
• Capture configuration decisions in rollout notes so support teams know what changed.
• Do not reuse one option for unrelated processes just because it is already configured.
• Review linked notifications, workflows, dashboards, and reports after changing this surface.
• Prefer narrow changes that can be tested with sample data before a tenant-wide rollout.
• When troubleshooting, start at the route users open, then inspect configuration, permissions, and logs in that order.
• Keep retired settings hidden or archived so users do not choose outdated paths.
• Assign an owner for ongoing review; unattended configuration becomes stale quickly.

For developers

Use these pages when the surface is read or changed by code, scripts, embeds, widgets, API clients, webhooks, or realtime listeners.

• /developer/data-hooks
• /reference/objects-records
• /reference/reports-dashboards
• /reference/field-selection

Related links

• /guides/records
• /guides/reports
• /guides/charts
• /guides/dashboards-dashlets