Saved analyses and business record links
Open Analytics → Saved analyses and business links and select an Agent with current data access. Saved analyses and record links have separate purposes: an analysis retains a question and calculation logic; a link records a reviewed relationship between two existing records.
Save and calculate an analysis
- Choose New private analysis and enter a clear question.
- Select Load approved metrics, then choose the intended metric and exact version.
- Set the business effective date and the definition’s exact parameters. If you attach source references, use references from permitted source reads; a reference is not a grant.
- Select Save private configuration, then Calculate with saved logic.
- Select a result version and Read my currently permitted result.
Each calculation keeps its configuration version, calculation time, and the agent and person who ran it. You can load earlier versions and compare accessible versions without replacing their saved definitions. Editing a draft does not rewrite a previously saved result version.
If calculation acknowledgement is lost, use Check saved run receipt for that same action before starting another calculation. A missing reply does not prove that no result was saved.
Publish without granting source access
Select a saved result version and the intended team readers, then choose Publish selected version. Show published link produces a link to that publication. Withdraw publication removes that shared publication; it does not delete its source systems.
The link shares the selected analysis and its fixed logic. It does not share the creator’s credentials, grant private database rows, or bypass source rules. A team reader receives a fresh calculation using their own current permitted view. That view may differ from the creator’s. The reader does not receive the creator’s hidden values or a comparison that reveals them.
The author can see saved result content only while the current permitted calculation still establishes the same result. Changes to source data or permissions can therefore change what is available when an old version is opened. A result version and its observation time are not a promise of permanently accessible historical data.
Review a link between records
Under Business record links:
- Select a configured record source and enter the original record’s identifier.
- Select the other configured source and its original identifier.
- Choose the relationship, enter the reason, and select Propose a link.
- Select Review both current originals and inspect the actual permitted records.
- Select Confirm reviewed link only when the reviewed pair and current proposal are still correct.
Available relationships include the same entity, client–contact, client–order, client–ticket, and order–invoice. Names that happen to match are not sufficient proof of identity. If originals have changed, update the unconfirmed proposal and review them again.
Use Find my saved links to return to an earlier link. Withdraw link reverses the association in AiHummer. Confirming or withdrawing a link does not merge records or write changes to the original systems.
Source requirements
Only configured, enabled sources with a supported current-reader path can be used. The built-in approved-record source maps an approved read-only database query to one record key and explicitly selected original fields. Database row-level permissions still apply.
A record kind such as “client” or “invoice” does not itself configure a CRM connection. A shared integration webhook is not proof of a person’s private record access. Unsupported sources remain unavailable; sharing an analysis or a link does not make them readable.
For metric definitions, see Approved business metrics. For reviewing many proposed results, see Batch data processing.