Skip to content
Dashboard
Set up HiVAM around your business · Chapter 4 of 4

Test permissions, trial access and your first useful AI question

A useful first AI experience starts with trustworthy records and a precise question. Ask about a job or exception you can independently verify, then open the cited records. Access depends on the organisation, user role, facility scope, capability and current entitlement. A broad trial should let the owner explore available capabilities, but it must not let a dispatcher see private payroll or another organisation’s data. Trial dates and recovery rights must be checked in the actual contract and deployed release.

HiVAM product guides · About 4 minutes to read, plus practice · Reviewed

Your learning goals

What you’ll learn

  • Test the intersection of role and entitlement.
  • Verify an AI answer against source records.
  • Plan a trial review without threats or surprise data loss.

Useful terms

Entitlement
The capabilities available under a contract or temporary grant.
Scope
The records or facilities a user is permitted to access.

Step-by-step operating routine

  1. Assign least necessary access

    Define the tasks of booking, dispatch, warehouse, finance and people staff. Give the appropriate facility and field access. Avoid shared administrator accounts, which prevent meaningful accountability.

    Record or confirm
    • User
    • Role
    • Facilities
    • Sensitive fields

  2. Test a restricted account

    Try permitted work and a prohibited record using an authorised test account. Check direct record access, searches, exports and AI as well as hidden navigation. A missing button is not an access control.

    Record or confirm
    • Allowed action
    • Denied action
    • Direct URL / API
    • Export test

  3. Prepare one verifiable AI question

    Choose a known date range and facility, such as deliveries waiting for POD review. Count the matching records yourself. Use clear terms rather than asking for a vague judgement about the whole business.

    Record or confirm
    • Question
    • Date range
    • Facility
    • Expected source set

  4. Check evidence and proposed actions

    Review sources, totals, time window and linked destinations. If AI proposes an action, inspect its affected records and current state before approval. A confident answer with unrelated buttons should be reported, not accepted as correct.

    Record or confirm
    • Source links
    • Filter basis
    • Proposed action
    • Reviewer

  5. Review trial use and ongoing rights

    Compare actual value with the chosen plan and tracker arrangement. Confirm renewal, downgrade, export and retention terms before expiry. Keep records accessible under agreed rights; do not assume a course page changes contractual retention.

    Record or confirm
    • Trial dates
    • Used capabilities
    • Contracted plan
    • Recovery terms
Worked example

The same question under two roles

An owner and a finance user ask which deliveries lack approved POD. Each answer must use only authorised records. The finance user should not gain unrelated payroll details, and neither user should see another tenant. Before approving a suggested follow-up, the system must recheck current permissions and record state.

  • Compare answers with independently counted records.
  • Test prohibited fields as well as pages.
  • Recheck rights when an action runs.

Exceptions and mistakes to avoid

  • AI must not invent sources, capability access or upgrade urgency.
  • Do not put API keys or personal documents into prompts.
  • Browser reading progress in this learning centre is separate from HiVAM organisation setup progress.
Put it into practice

Access and AI acceptance sheet

Use approved test accounts and fictional sensitive records. Test access through multiple surfaces without exposing actual private data.

Illustrative row—replace it with your own private operating information.
RoleQuestion / actionExpected permitted recordsObserved resultIssue owner
FinancePOD waiting reviewPermitted facilities onlySource links checkedAdministrator
Download CSV worksheet

Includes the illustrative row and blank rows. This is a planning worksheet, not a HiVAM import format. Keep your completed copy private; do not add credentials.

Check your understanding

Try answering first, then open the explanation. Use the worksheet and source records to practise the task.

Does full trial access remove role limits?

No. Temporary capability grants must still intersect with user and tenant permissions.

What is a good first AI question?

A specific operational question with a date range, scope and record set that you can independently verify.

Connect the workflow

Put it to work with HiVAM

Use these connections to explore the relevant product workflows. Confirm access in your deployed release; API capabilities require an integration or an available interface.

Platform capability · Starter and above

Ask AI with evidence and reviewed proposals

Use evidence-linked answers and reviewed proposals; verify source links and action scope.

Platform capability · Starter and above

Trial rights, downgrades and recovery

Check the actual trial, downgrade and export rights instead of assuming a fixed grace period.

Compare all capabilities and availability

Keep your learning moving.

0 chapters marked complete. Reading progress stays in this browser; it is not a qualification or your company’s setup progress.

Try the workflow with your team.

Bring a representative job and an exception to a HiVAM demonstration. Review saved records, permissions and handoffs alongside the interface.