Answers for every part of ZoneProof.

For: Administrator · Evidence lead

Administrators and evidence leads can add a site in Team & sites. Duplicate exact names are rejected. Use those same names in imports, mappings and scoped claims so coverage can match them. Site rename/delete is not exposed as a general self-service workflow; agree an audited correction with the maintainer rather than creating misleading duplicates.

For: Administrator

An administrator can update the organisation name and Investigation start policy (days) in Administration. The allowed policy input is 0–90 days. It affects later draft verification; it does not rewrite a previously published report. The field is your configured review criterion, not a legal deadline supplied by ZoneProof.

For: Everyone

The ten implemented check families cover licence currency against roster dates, exclusion-zone alerts/actions, inspection site/month/type coverage, training completion, incident closure evidence, corrective-action verification evidence, overdue imported actions, investigation lag/escalation, director briefing records and policy source attachment.

Some checks run only when the matching claim type exists; others assess supplied periodic records. One family can generate multiple findings. Use the check reference in How to and read each result's scope and limitations.

For: Everyone

The interface groups implemented checks into its six officer-duty headings. A group is Gap if it has no findings or any Contradicted/Unverified finding, Partial if it otherwise contains a Partial result, and Evidenced when all its findings are Verified. Priority matters sort by evidence status and the implemented risk significance. These are reporting summaries of supplied checks, not legal conclusions or independent assessments of every duty.

For: Everyone

The views use different implemented windows: Evidence health highlights licences expiring within 30 days after its reporting cutoff. The licence-currency verification finding separately reports a 60-day expiry look-ahead and checks expiry against supplied roster-shift dates. Compare the actual window and cutoff rather than expecting identical counts.

For: Everyone

ZoneProof connects management claims to supplied evidence, records board questions and preserves published reporting snapshots. Its assurance workspace adds control reviews, attestations, owned actions, meeting briefings and controlled external sharing.

Findings describe the supplied records and their scope. They do not certify legal compliance, guarantee workplace safety or establish that every relevant record was supplied.

For: Administrator · Evidence lead

Confirm the organisation, add sites, invite colleagues and at least one director, then create a reporting period. Import representative evidence, record management claims, review health and run verification before publication. Invite another administrator or evidence lead if independent action/control review is needed.

For: Everyone

A newly created organisation has no reporting data. Create a period first; then upload or import evidence and run verification. Review rooms require a published report, and report comparisons need an earlier published period for a baseline. Merely opening a page does not complete a setup task.

For: Everyone

Use FAQ for explanations and How to for tasks. Search by topic, choose a category or audience, and expand an entry. Each entry has a permanent link and related help. Print / save PDF prints the current results with the entries expanded. Help is available before sign-in; opening a workspace feature still requires the appropriate access.

For: Everyone

New companies can choose Register on the public website to request a pilot workspace. The team reviews the request before sending an invitation; submission does not create a login. If your organisation already uses ZoneProof, ask its administrator for a named invitation from Team & sites. Accept the invitation, choose your own password and sign in with the invited email.

For: Everyone

Invitations expire after 48 hours, are single-use and can be revoked. A resend replaces the previous link. Ask the issuer to resend and open the newest email. If you refreshed the password-selection page, reopen the email because the link fragment is removed from the address bar. Existing accounts cannot be overwritten or moved by accepting an invitation.

For: Everyone

Select Forgot password? on the login page and enter your account email. If the account is eligible and delivery is available, a link arrives with a 30-minute lifetime. Choose and confirm at least 12 characters, within 72 UTF-8 bytes. Successful recovery revokes existing sessions and older recovery links; then sign in with the new password.

For: Everyone

Check the exact account address, spam folder and newest email. A reset request deliberately gives a neutral response for unknown, inactive or throttled accounts. Repeated requests can be limited; wait before retrying. Ask an administrator to check account status and the technical maintainer to inspect the verified sender, email-provider delivery logs and canonical hostname. Provider acceptance does not prove inbox delivery.

For: Everyone

Reset links expire after 30 minutes and stop working after successful use, another completed reset, a password change or account deactivation. Refreshing the form removes the in-memory token; reopen the original email while valid. Request a new link when necessary. Never paste a recovery link or password into a support message.

For: Everyone

Use the exact invited email and check that the account is active. Login is throttled after repeated failures; retry after the stated 15-minute window rather than repeatedly submitting. Use password recovery if needed. A successful password change or administrative disable signs out prior sessions. Bootstrap deployment settings cannot reset an existing account.

For: Everyone

Open Your account and enter your current password plus a new password of at least 12 characters. Save it and sign in again. The change invalidates every prior session on its next request. Use Forgot password? if you cannot supply the current password. Use a long unique password and never share an account.

For: Everyone

Administrators manage organisation settings, invitations, account access, integrations and external sharing. Administrators and evidence leads manage sites, draft evidence/claims, verification, publication, controls, attestations and follow-up assignments.

Directors read board evidence, ask Director Q&A questions and acknowledge published reports. Any active assigned owner can progress their own follow-up work. Directors/administrators can challenge another manager's attestation and seal meeting packs; only independent administrators/evidence leads accept control or action submissions. A technical maintainer is a help audience, not an application role.

For: Everyone

Workspace membership is organisation-wide in this release. Selecting a site on a control or an import limits that item's scope; it does not create site-level access permissions. Group oversight is also an explicitly granted organisation-wide read-only scope. Per-site and field-level authorisation are not implemented.

For: Administrator

Only administrators issue, resend and revoke invitations. Team & sites invites people into the current organisation. Administration → Create an organisation creates a separate workspace and invites its initial administrator; the issuer stays in their own organisation and does not automatically gain access to the new company's evidence.

For: Everyone

User emails are globally unique. An invitation cannot change an existing person's organisation, role or password. General multi-organisation membership and tenant switching are not available. A named existing account can instead accept explicit, expiring read-only group oversight grants from other companies.

For: Administrator

An administrator can use Disable & revoke sessions in Administration for another user. Existing sessions fail on the next request. Reassign outstanding follow-up work and active controls; retain historical evidence and acknowledgements. The app prevents self-deactivation. Grants and rooms issued by an administrator also depend on that issuer remaining active and authorised.

For: Everyone

Draft periods accept evidence and claim changes and verification reruns. Publication seals the report evidence, findings, claim scope and director roster. Published reports accept continuing board dialogue and acknowledgements without rewriting their original evidence. A period becomes Signed when every director on its publication roster has acknowledged it.

For: Administrator · Evidence lead

Create the reporting month and the records-to cutoff that match your intended evidence snapshot. Use Overview → Reporting periods links to open that specific period's uploads, claims or report. The main board report normally selects the latest published/signed period, or the latest draft if none is published; this can differ from the latest draft in the change briefing.

For: Everyone

Published evidence and findings are sealed. There is no self-service rewrite or deletion of that report. Use a new draft/reporting period for corrected or later evidence, explain the change and retain the original trail. Later source imports, control reviews and action closures do not silently alter published findings.

For: Everyone

The eight structured sources are Inspection, CorrectiveAction, Incident, Licence, TrainingRecord, RosterShift, CameraAlert and DirectorBriefing. Each has a downloadable CSV template with exact column names. The current upload workflow accepts CSV records, not arbitrary PDF, Word, photo, video or email attachments.

For: Administrator · Evidence lead

Start with the matching template, preserve its header names and provide a stable source id for each row. Use ISO dates such as 2026-10-22, exact enum values and true/false where required. A blank optional date is different from a fabricated date. Uploads must be .csv and at most 10 MB. Fix every parse/row error before confirmation.

For: Administrator · Evidence lead

An exact normalised file duplicate for the same organisation, period and evidence type is rejected. CSV snapshots are otherwise append-only: a different overlapping export can add duplicate business records. Source id alone does not make CSV imports update existing rows. Review scope before importing and use the integration revision workflow for ongoing source updates.

For: Administrator · Evidence lead

Preview must contain at least one row, no parser errors and no invalid rows. Check required headers, real ISO dates, allowed enum/boolean values, file size and evidence type. Only an administrator/evidence lead can import to a draft. If the period was published while you prepared the file, select a new draft and preview again.

For: Everyone

Published reports preserve the records used at publication. Action closure, control checks and attestation submissions copy focused supporting uploads into their own retained snapshots. Later source edits do not replace those copies. These records are limited by what was supplied and by application/database trust; a stored fingerprint is not independent proof that the underlying event was true.

For: Everyone

Action, control, attestation and meeting-response captures require 1–1,000 actual records and a payload no larger than 2 MB. A regular CSV import can be larger, but a supporting snapshot must be focused. Prepare an appropriately scoped upload first. Rooms and sealed meeting packs also have overall size limits; split large reviews into focused packs.

For: Everyone

Management claims are typed statements the verification engine compares with evidence in a draft report. Attestations are a responsible manager's retained, qualified confirmations for a period and scope, with separate director challenges. An attestation does not automatically become a verified engine finding or rewrite a report.

For: Administrator · Evidence lead

The current types cover all licences current, exclusion zones implemented, inspections complete, training complete, incident closure and policy updates. Enter the statement and exact site scope or all. Relevant fields include the claimed training percentage/course, inspection type/month, and policy source reference. Editing a claim clears old findings; run verification again.

For: Everyone

Verified means the implemented check is supported by the supplied records in its stated scope. Partial indicates mixed or incomplete support. Unverified means there is insufficient supporting evidence for that check. Contradicted means the supplied evidence conflicts with the assertion or criterion. Read each finding's explanation, source records and limitations; no status certifies overall safety or legal compliance.

For: Administrator · Evidence lead

Run verification after importing or changing draft evidence or claims, and before publishing. Stored findings do not update just because a source system changed. Publication requires at least one finding and a director roster. A blank findings list is not an assurance result. A new source revision in a published period requires a new draft instead of modifying that report.

For: Administrator · Evidence lead

Only administrators/evidence leads can publish a draft. At least one director must have accepted their invitation and be on the roster, and verification must produce findings. Check the selected period; Published/Signed periods cannot be published again. An outstanding invitation alone is not an active director.

For: Everyone

No. Headline percentages weight findings equally and relate to the implemented evidence checks. Training completion uses the supplied training register, including incomplete rows, not an independently established workforce denominator. Policy attachment confirms a reference record, not policy quality or implementation. Read missing sources and limitations alongside the numbers.

For: Everyone

Open the intended period's Board report and use its PDF export or print view. The PDF is a board-report export; a sealed meeting briefing has its own PDF/HTML exports. If rendering fails, retry after the free service wakes and ask the maintainer to check renderer resources and the canonical HTTPS address. Never make a private report public to work around a download problem.

For: Everyone

It compares the selected period with the latest earlier published/signed month in the same organisation. Check meaning, duty and claim text/scope are matched rather than regenerated row IDs. A removed check is not treated as resolved. Without a baseline, the page describes current concerns. Overdue actions and unanswered questions are current workspace activity, distinct from historical report evidence.

For: Everyone

The Director Q&A form is for the Director role. Administrators and evidence leads record management responses and may link same-period Finding IDs copied from the report verification table. The response evidence status is derived from those findings. An administrator can challenge attestations, but that is a separate workflow from asking Director Q&A questions.

For: Director

No. Acknowledgement records that a rostered director reviewed the published report; it does not endorse management's accuracy. It is retained in the ledger. Only a director on that report's frozen publication roster can acknowledge it. A later invited director is not automatically added to a historical roster.

For: Everyone

No. Director Q&A, follow-up closure and attestation challenge resolution are distinct workflows. A written response may still have unverified evidence. Follow-up closure needs supporting records and an independent reviewer; an attestation challenge needs its original challenger to review the response and resolve it.

For: Everyone

It shows supplied-source coverage, fixed freshness checks, licence expiry, incomplete training rows and site appearances at the selected reporting cutoff. Drafts use current records; published/signed reports use sealed evidence. Current integration connection health appears separately. Received records do not establish complete coverage, operational effectiveness or a risk rating.

For: Everyone

Missing means no rows for that source. Inspection, RosterShift, CameraAlert and DirectorBriefing freshness uses the latest usable date up to the records-to cutoff; older than 30 days is stale, and no usable date is flagged separately. Records after the cutoff need review. The threshold is a pilot review prompt, not a company-specific inspection schedule.

For: Everyone

Health uses the selected report's supplied rows and cutoff. It counts expired licences, those expiring within the following 30 days, and training rows without a completed date. It does not infer missing workers or an independent total workforce. Match period, source coverage and denominator before comparing another system's figures.

For: Everyone

No. Imported CorrectiveAction rows are source evidence used in verification. Follow-up actions are workspace assignments with an owner, deadline, evidence submission and independent review. Completing a workspace action does not change imported evidence or automatically mark a published finding verified.

For: Everyone

Administrators/evidence leads assign actions. Only the current active owner can start and submit their open work. A different administrator/evidence lead, who is neither owner nor submitter, approves or returns an In review action. Managers can reassign Open/In progress work or reopen a Closed action with a reason.

For: Everyone

Due dates are calendar dates in Australia/Sydney. An unclosed action becomes overdue on the following Sydney calendar day. Closed actions are not overdue. The current release does not offer a per-organisation timezone setting. Changing deadlines requires a manager and preserves the reason in history.

For: Everyone

Closure deliberately separates the person doing the work from the person accepting the evidence. Ask another active administrator/evidence lead in your organisation to inspect it and record a rationale. Reassigning an action does not let its original submitter approve their own evidence. Do not share accounts to bypass independent review.

For: Everyone

A returned submission goes back to In progress with the review explanation. Its captured evidence and earlier history remain available; the owner can provide a new focused submission. A manager can reopen a closed action with a reason. Stale version messages mean another change occurred: refresh and review before resubmitting.

For: Everyone

The latest submission determines the state. No submission is Missing; a pending submission is Awaiting review. A returned check or a recorded gap remains a Gap. An independently accepted supporting observation is Current through its observation date plus the defined review frequency, and Stale after that date. Archived controls retain history. Current does not certify effectiveness.

For: Everyone

An administrator/evidence lead defines the owner, optional site, review criteria and a frequency of 1–365 days. The owner submits a non-future observation date, a supported/gap assessment, a meaningful explanation and a captured upload. A different administrator/evidence lead accepts or returns it. Owners can be changed and controls archived; past observations are retained.

For: Everyone

Yes. Accepting a review means accepting the recorded assessment and its evidence; it does not turn a recorded gap into a supported control. Address the issue, assign follow-up work if needed and submit a later observation. A new pending submission is shown as pending rather than silently retaining a green Current state.

For: Everyone

The responsible manager can choose Confirmed, Qualified or Unable to confirm and explain the basis, scope and limitations. Confirmed/Qualified require captured supporting evidence. Unable to confirm may explicitly have none. Each revision is retained, and later confirmation does not erase earlier qualifications or resolve old challenges.

For: Everyone

A director or administrator can challenge someone else's submitted revision. Only the assigned statement owner responds. The original challenger resolves it after a response, with a rationale. The challenge stays bound to the exact revision; another administrator cannot silently resolve someone else's question.

For: Administrator · Evidence lead

Retain the original statement and revision history and request a new attestation from the successor. Current statement ownership is not silently rewritten. Disable the leaver's access through Administration. Follow-up actions and active controls have their own reassignment workflows.

For: Everyone

No. Each subsidiary's administrator offers an explicit expiring read-only grant to a named active ZoneProof account in another organisation. The recipient must accept it in Group oversight. Company names, shared domains and an account's home role do not automatically grant cross-company access.

For: Everyone

The accepted grant shows organisation-level summaries, the latest published report, site evidence coverage, published supporting records and current action summaries. It does not permit editing the other company's data, viewing its draft evidence, managing integrations or using its normal meeting-export APIs. The grant is organisation-wide rather than site-specific.

For: Everyone

The grant may be unaccepted, expired or revoked, or its issuing administrator may have been disabled or lost the Administrator role. Oversight is checked again on each request. Ask the subsidiary's authorised administrator to review it. Your normal home workspace membership is separate.

For: Everyone

Select report findings, director questions, follow-up actions, attestations or critical controls. The selected source state is captured when added. Assign a response owner and explain what management should address. That owner can answer and optionally attach focused evidence while the meeting is Draft. Later source changes do not silently replace captured issues.

For: Everyone

No. A director/administrator seals a pack containing at least one issue. Requests, responses and captured response evidence are frozen with a consistency fingerprint. Unanswered requests stay explicitly unanswered. Create a later meeting for additional developments. A sealed meeting pack is separate from a published board report and is not independently Polygon-anchored.

For: Everyone

A sealed meeting provides an A4 PDF and a standalone printable HTML briefing. The export includes captured source status, requests, supplied responses, source references and response evidence. If PDF rendering is temporarily unavailable, use the printable HTML. A draft must be sealed before these export links appear.

For: Everyone

An administrator shares a frozen published-report summary containing findings, claims and evidence health, plus only the raw report uploads and sealed meeting packs deliberately selected. A selected meeting pack includes its captured sources and response evidence. The recipient receives no normal workspace account or general editing access. Preview personal/confidential information before authorising disclosure.

For: Everyone

The room expires after the issuer's selected 1–30 days. The emailed link can be redeemed once and creates a room-specific browser session lasting at most seven days or the room expiry, whichever is sooner. Refreshing the entry page loses its fragment; reopen the unredeemed email link. After redemption, use the same browser. A lost session or new device requires a replacement room from the issuer.

For: Everyone

An administrator can revoke both the unused link and future browser access immediately. The issuer must remain active and authorised. Access history records redemption and content views. Revocation cannot recall copies a recipient already saved, and email-link possession is not MFA or a verified identity check. Do not forward confidential links.

For: Everyone

Creation requires Administrator access, a published/signed report, a working email sender, an explicit disclosure confirmation and a named recipient. Up to ten sealed report uploads and ten sealed meeting packs can be selected, within an 8 MB room payload. Rooms are limited to ten creations per organisation/hour. Delivery failure revokes the room. Expired/redeemed/revoked links and mismatched browsers cannot grant access.

For: Everyone

The working common Evidence API accepts client-managed CRM/automation exports. HubSpot has a native OAuth-ready read connector for contacts/companies with evidence-property mapping, but requires registered provider credentials and client acceptance. Salesforce, Dynamics and SafetyCulture do not have native sign-in connectors in this release; use CSV or client-managed automation through the Evidence API.

For: Administrator

The HubSpot connector requests read permissions for contacts and companies; provider consent may cover the whole authorised account, not only a chosen site. ZoneProof's mapping/site/date filters limit imports, not the provider's permission grant. Review the consent screen and request the minimum practical scope. Credentials stay server-side; clients can pause/disconnect access.

For: Administrator

Preview checks exact source keys, target types, required fields and selected period/sites/history. At least one valid in-scope row and no rejected rows are required. Approval is bound to those exact settings and expires after 15 minutes. A sample is previewed, not automatically imported. Choose properties that genuinely represent safety evidence, rather than ordinary contact details.

For: Administrator

No. Each new draft period needs explicit selection and a fresh preview. An imported connection's evidence type cannot be changed, and narrowing imported scope does not delete prior evidence. Use a new draft for changed period scope/mapping. Published report records remain sealed when the source changes.

For: Everyone

No. It means the event was queued. Poll the job-status endpoint or inspect Integrations for completion, rejected rows and retries. The free pilot attempts request/manual processing and offers Process now, but its alert scheduler does not run integration reconciliation. Continuous imports/retries and HubSpot reconciliation need an operating integration worker.

For: Administrator

Keep stable source-record IDs and a stable event ID for a retried identical batch. Reusing an event ID with changed content conflicts. Correct rejected data at source and submit it under a new event ID. Source content hashes track current draft records and retained revisions; published evidence is preserved. Send complete mapped records rather than sparse patches.

For: Administrator

Inspect the connection, job status and row-level results. Correct mappings, dates, enum values and unknown sites at source; then submit a corrected event with a new ID. Resolve temporary/provider or period-state issues before using Replay/Process now. A next-sync timestamp is an intended attempt, not proof that a worker is running. Last successful sync is the confirmed completed read/import, not just a scheduled time.

For: Administrator

Controlled write-back sends an explicitly approved signed request to an allowlisted client automation endpoint. The receiver performs the provider-specific task/link update and must deduplicate requests. Source evidence remains owned by the source system; only agreed ZoneProof-owned task/link fields should be updated. There are no unrestricted native CRM writes or automatic approval of safety evidence.

For: Administrator

Pausing cancels pending jobs/deliveries and revokes incoming API keys; an in-flight operation may still finish. Disconnecting removes saved credentials, signing secrets and the write-back destination while retaining imported evidence, revisions and history. Also revoke the app in the provider account when appropriate. Re-enabling an API connection rotates its incoming key.

For: Everyone

Both an administrator's organisation automation policy and your own email preferences must be enabled in Assurance workspace → Alerts. They default off. Check current membership, due dates and delivery status. Assignment/change emails are separate from scheduled reminders. Provider acceptance does not guarantee inbox delivery, and the free scheduler is best effort rather than an emergency alert service.

For: Everyone

The configured daily job checks at 22:17 UTC: 08:17 Sydney standard time or 09:17 daylight time. Owners can receive due-soon reminders and weekly-deduplicated overdue reminders. Opted-in independent administrators/evidence leads receive escalation notices after the configured overdue delay. A digest is keyed to the Sydney week and catches up on the next successful run; it is not guaranteed to arrive on a particular weekday.

For: Everyone

Queued waits for processing; Retry has a stored next-attempt time after a temporary failure. Up to five attempts are made. Failed needs operator investigation, including expired final delivery leases. Sent means the email provider accepted it. Cancelled means delivery is no longer appropriate, for example because an action closed, changed owner/deadline or the recipient opted out. A bounded pass processes up to 50 jobs.

For: Everyone

Yes. Save your own reminder/escalation and digest preferences in Alerts. An administrator can disable organisation scheduled delivery for everyone. These settings control scheduled notifications; immediate invitation, recovery and action-change messages have separate purposes. Existing delivered mail cannot be recalled.

For: Everyone

No. It retrieves supported evidence categories deterministically and provides source links, cutoff/as-of dates and limits. Current questions cover overdue actions, coverage/freshness gaps, unanswered director questions, controls needing attention, attestations/challenges and report concerns. It does not send prompts/evidence to an external AI model or answer arbitrary predictions.

For: Everyone

It can show report concerns with sites found in explicitly linked source records. Those records may include activities that passed, so they are not automatically the locations of failures. Findings with no linked site record remain unassigned. Read the finding and its stated scope; this is not a complete site-level finding count or risk ranking.

For: Everyone

Unsupported questions receive a request to rephrase. Empty results mean no matching supplied records in the selected scope, not proof that risk is absent. Check the selected period, evidence coverage and verification first. Results show up to 100 records with the total; open the source pages for full context.

For: Everyone

The ledger links publication, question, response and acknowledgement records using hashes and sequence. Verify chain checks consistency of that stored chain. A privileged database operator could rewrite an unanchored chain. External Polygon comparison can add an independent digest reference, but neither hashing nor anchoring proves the truth of management's assertions.

For: Everyone

No. Read the actual network/anchor status in Integrity ledger. The current free pilot leaves Polygon disabled pending separate Amoy activation and funding. Report ledger anchors are different from control/attestation/action/meeting fingerprints, which are not independently anchored. Never describe Not anchored or Queued as confirmed on-chain.

For: Everyone

The anchoring design publishes a cryptographic digest in transaction data, not the evidence rows, personal records or report contents. Anchoring uses a dedicated signer and pays network gas. Amoy is the initial test target; mainnet is separately gated. Keep the signer key outside the web/client browser and independently preserve the trusted public signer address.

For: Everyone

Download the selected ledger entry's proof and preserve it with its trusted signer and network details. The technical verification command checks the stored ledger data and, when anchored, fetches the transaction/receipt from the configured network. It needs an independently trusted signer address; trusting a signer value taken only from the same application database is not independent verification.

For: Everyone

Normal access is organisation-scoped and role-checked. Explicit group oversight grants expose the stated read-only company scope; external rooms expose the selected frozen material. Transactional email providers receive addresses and account/action access messages. The evidence assistant uses no external model. Blockchain anchoring publishes a digest when enabled. Review connected provider permissions and your organisation's disclosure policy before sharing.

For: Everyone

SSO/MFA and site/field-level permissions are not implemented in this pilot. The current hosting setup is not an Australian data-residency commitment. Do not infer certifications, retention guarantees or availability SLAs from the interface. The technical maintainer should validate security, backup recovery, residency and capacity against client requirements before wider rollout.

For: Everyone

Published reports, ledger history and captured submissions are preserved by the application; there is no general self-service purge or complete organisation-export workflow. Report PDFs, meeting PDF/HTML and ledger proofs are targeted exports. Ask your administrator and technical maintainer to handle approved retention, complete export or deletion requests using an auditable procedure that preserves required records.

For: Everyone

Do not send passwords, reset/invitation/review-room links, API keys, OAuth tokens, database URLs, signing secrets, private wallet keys or unredacted evidence. Share the page, approximate time and timezone, non-secret record/job ID, visible error, role and redacted screenshot. Use an approved secure channel if an authorised investigation needs private records.

For: Everyone

The pilot uses free web/database services that can sleep or scale down while idle. The first request may need time to wake; retry after it has started. Large exports and concurrent work can be constrained. This is best-effort pilot hosting, not guaranteed production availability. Check provider status and application readiness if the delay persists.

For: Everyone

No paid upgrade or new AI account is introduced by these workflows. Hosting, database, email and private-repository Actions still have provider quotas. Polygon anchoring, when deliberately enabled, needs funded network transactions. A technical maintainer should review current limits and obtain the owner's approval before adding paid resources or enabling mainnet.

For: Technical maintainer

The technical maintainer must configure and test the database backup/retention procedure; a working application is not proof of a recoverable backup. Preserve evidence revisions, captures, ledger, room/meeting payloads and required secrets separately. The application is portable Docker/Node/PostgreSQL. Verify a replacement deployment before changing DNS or revoking the old host.

For: Administrator · Technical maintainer

The private GitHub repository is the source of truth, and Render follows main after CI checks. Use a reviewed pull request for changes, keep runtime credentials in the hosting environment and let startup apply additive migrations. GitHub access is separate from an application login and must be granted by the repository owner.

For: Administrator · Technical maintainer

No. The notification scheduler runs the reminder/digest outbox. Continuous connector reconciliation, timed integration retries and approved outbound delivery need the integration worker. The free pilot uses request/manual controls instead. These are different queues with different operational checks; a healthy alerts job is not proof of CRM sync liveness.

For: Technical maintainer

Use a verified sending domain and a sending-only Resend key scoped to it, kept in the hosting environment. Configure the sender and canonical HTTPS application URL, redeploy and verify delivery to a consenting inbox. Keep link tracking off for fragment-based access links. Website DNS and email-sender verification are separate tasks; use the provider's exact current DNS values.

For: Everyone

Contact your organisation administrator for invitations, membership, permissions and workflow ownership. Ask the technical maintainer about hosting, email delivery, queues, backups and provider configuration. ZoneProof does not currently include a built-in support ticket service or a published response-time guarantee. Use the redacted diagnostic checklist in the support guide.