Admin how-to

Publish clean outputs and keep external links observable.

Reports and exports are what many customers actually receive. Integrations are what many office teams depend on behind the scenes. Treat both as operational surfaces, not afterthoughts.

Audience

Admins, report reviewers, and office teams responsible for client-facing output or system connectivity.

Before you start

You need completed inspections or live site data for outputs, and the relevant access level for integrations or API features.

Expected outcome

Your exported documents reflect current operational data and your system connections remain explainable when something goes wrong.

Generate client-ready reports

Open Reports and choose the site that matches the output you need to produce.
Use preview workflows for high-value outputs before generating the final download.
Generate only after the inspection data, defects, and branding context are current.
Use the matching output for the job: compliance report, defect summary, certificate bundle, or asset register export.

Deucalion admin reports workspace — **Reports workspace**
Use previews for higher-risk outputs and quick download when the underlying data is already trusted.

Export operational data deliberately

Use CSV exports when another team needs structured data, not when a PDF would communicate the outcome better.
Keep site naming and organization naming accurate before exporting so downstream consumers do not inherit stale labels.
When a customer needs a document pack, prefer the report/certificate routes over piecemeal file hunting.

Manage connected systems with visibility

Use Connected Systems and Integrations to monitor connection health, sync history, record links, and conflicts.
Run manual syncs only when you understand why they are needed; use the sync log and linked-entity views to explain the state first.
Resolve conflicts before office users start duplicating updates in both systems.
Use the connected-system surfaces as your operational evidence trail when someone asks whether Deucalion or the external system is authoritative for a given record.

Use API keys and API docs safely

Open API Keys only when you need a scoped integration credential rather than sharing a user login.
Create keys with the minimum scope required and record who owns the integration that uses them.
Use the public API documentation at /api-docs when you need the current request and response contract.
Rotate or retire keys when integrations change ownership or are no longer in active use.

What is intentionally excluded here

This guide does not cover platform-only internal tooling such as report intelligence, knowledge-base operations, feature flags, health, app versions, or embed ops.

Troubleshooting

Problem	What to check
The downloaded report looks outdated	Confirm the site, organization, inspection, and defect data were updated before you generated the output.
An integration sync looks wrong	Check sync history, linked entities, and conflicts before re-running the connection blindly.
An API integration needs the request format	Use /api-docs instead of reverse-engineering from the UI or old examples.

Next steps

Use the shared reference and troubleshooting pages when you need definitions or symptom-based fixes rather than a workflow.

Shared reference page Troubleshooting

Last updated: .