Property & Compliance Management

Troubleshoot Real Estate PDF branding/output

Check source data, template/hook context, image file and PDF engine logs.

Reviewed 27 October 2026Merged module 2.1.3
Where to goSource record → PDF

Before you start

Use the relevant record permission. Workspace mail, branding and API configuration require administrative access.

Follow these steps

  1. Open the source record or configuration named in the route.
  2. Check source data, template/hook context, image file and PDF engine logs.
  3. Test admin, client and broker contexts separately.
  4. The actual output belongs to the intended workspace and source record.

Fields, rules and limits

  • Test admin, client and broker contexts separately.
  • PDFs use the workspace company identity and local branding assets. A remote logo URL is not automatically fetched as a local PDF logo; check the generated file itself.

Check it worked

The actual output belongs to the intended workspace and source record.

If something does not look right

If the expected result is missing, check the saved record, the current workspace and the action’s permissions. Record the exact validation message; do not repeat a state-changing action until you know whether the first attempt saved.

Questions and answers

What should I verify for this task?

Test admin, client and broker contexts separately. PDFs use the workspace company identity and local branding assets. A remote logo URL is not automatically fetched as a local PDF logo; check the generated file itself.

Why is the record or action unavailable?

Use the relevant record permission. Workspace mail, branding and API configuration require administrative access. Check the current company and record relationship before requesting additional access.