InfiniHash App Store Multi-Client Workspace Setup (Onboarding)

InfiniHash App Store Multi-Client Workspace Setup (Onboarding)

1. 01

   Create the email-and-password account on the InfiniHash App Store and open the free tier of AttestProof, BankChangeProof, and ControlLedger

   Confirm which client engagements need user-access evidence, vendor bank-change verification, or recurring control attestation before any paid tier is purchased. Vendor costs sit in the pricing tiers field; do not carry them into client pricing.

2. 02

   Provision a separate workspace per client inside the App Store

   One workspace per engagement keeps AttestProof review campaigns, BankChangeProof vendor records, and ControlLedger control schedules from bleeding across accounts. Agencies running several retainers should name each workspace after the client entity, not the internal team.

3. 03

   Map the client's user-access CSV into a per-reviewer review campaign in AttestProof

   AttestProof Starter covers 5 systems and up to 1,000 rows per review with email invites and reminders. Anything past those ceilings pushes the engagement to AttestProof Pro at $79/month for unlimited systems and rows.

4. 04

   Load vendor bank records into BankChangeProof and switch on forced callback plus second approval

   BankChangeProof Team at $39/month handles up to 250 vendors and 5 users. The forced callback and second-approver path is what turns a bank-detail change into a dated proof artifact rather than an email thread.

5. 05

   Build the recurring control calendar in ControlLedger and attach client co-sign reminders

   ControlLedger Solo is the entry point for recurring control attestation. Schedule each control at its real cadence so the Evidence Packs land before the auditor's fieldwork window, not during it.

6. 06

   Connect the client's Microsoft 365, Google Workspace, Gmail, or Stripe account to the relevant app

   These four integrations are the ones the App Store supports. Confirm the client's stack matches before promising automated evidence capture; a mismatch means manual CSV uploads each cycle.

7. 07

   Run one full review cycle end to end and export the proof pack

   AttestProof Starter exports CSV; Pro adds auditor share links, JSON export, your logo on packs, and 5 team members. Validate the artifact with the client's auditor before the retainer goes live.

8. 08

   Document the monthly delivery rhythm and hand the workspace to the delivery owner

   Record review completion monitoring, reminder cadence, and export timing in the client runbook. The handoff note should name who watches ControlLedger schedules and who chases late reviewers.