Zipwire Documentation
Visit Zipwire
  • ๐Ÿ‘‹Welcome to Zipwire
  • Overview
    • ๐Ÿ’กWhat is it?
    • ๐Ÿ™‹โ€โ™€๏ธWho can use it?
    • โœจOur Features
    • ๐Ÿš—Can I test drive it?
      • ๐Ÿ“ฆSetting up Zipwire Approve
      • ๐Ÿ“ฅSetting up Zipwire Collect
    • ๐Ÿ”‘Logins & Invitations
    • ๐ŸขZipwire Collect: Rapid Onboarding, Effortless Compliance
    • ๐Ÿ’พData Ownership in Zipwire
  • Zipwire Approve
    • ๐Ÿ…How Zipwire Approve is radically different and speeds up pay day
    • โ›”Why we don't track start and end times
    • ๐Ÿ“ฆUnboxing key concepts
      • ๐Ÿ“œAccounts
      • โฒ๏ธTimesheets
      • ๐Ÿ‘ทSenders
      • ๐ŸšฆApprovers
      • ๐Ÿ‘‘Processors
      • โคต๏ธWorkflows
      • ๐Ÿท๏ธAssignments
      • ๐Ÿ“Billing Plans
      • ๐Ÿ’ฑRate Plans
      • ๐Ÿ“ฌTeams & Inboxes
      • ๐ŸขWorkplaces
      • ๐Ÿ›ก๏ธClients
      • โœ๏ธThe Journal
      • ๐ŸคธActivities
      • ๐Ÿ’ธPayment Methods
    • ๐Ÿ”ฒLogical structure
    • ๐Ÿ› ๏ธSet up your workplace
    • ๐ŸšฅProcessing stages
    • ๐Ÿ’ตUnderstanding invoicing
    • ๐Ÿท๏ธUsing assignments
      • ๐Ÿ–๏ธHoliday assignment
  • Zipwire Collect
    • ๐Ÿ—„๏ธEffortless Document Collection for Any Need
    • ๐ŸŸขGet Started
    • ๐Ÿ˜ญIDSP, IDVT, KYC, KYB and AML
      • ๐ŸคณSelfie Checks Powered by Yoti
      • โ›“๏ธBlockchain Attestations
    • ๐Ÿ“„Using Packs
    • ๐Ÿค–Machine Vision
      • ๐ŸคทFailure to Recognise
      • ๐ŸชชDocument Types
    • โœ๏ธManual Entry for Streamlined Information Gathering
    • โœจCreating a Collection with AI
    • ๐Ÿ‘€What the Respondent Sees at Their End
    • โ™ป๏ธLifecycle of a Collection
    • ๐ŸššBulk Upload
    • ๐Ÿ”Document Inspection
  • Fundamentals
    • ๐Ÿ›ก๏ธSecurity
      • ๐Ÿ“ฒAuthenticator mobile apps
      • ๐Ÿ”Two factor in Zipwire
      • Wallet Connections
      • Sign-in with Ethereum
      • Attestations
        • The "IsAHuman" Attestation: Purpose and Limitations
        • Zipwireโ€™s Master Attester Wallet Address and Public Key
      • Wallet Verification Guide
        • Introduction to Sleeper Wallets and Blockchain Legends
        • How Sleeper Wallets Are Created
        • Verifying Attested Wallets
        • The Market for Selling and Buying Attested Wallets
        • Holistic Evaluation of Ethereum Wallets
        • The Future of Attestations and Wallet Verification
        • Verifying Zipwireโ€™s Merkle Root Attestations for Developers
      • Understanding Merkle Trees and Proofs
  • Use Cases
    • ๐ŸŽญIdentity Checks - Right to Work
    • ๐ŸชชCompliance - Know Your Customer
    • ๐ŸŽจFor Senders
      • ๐Ÿ’ฌSending journal updates via WhatsApp
      • ๐Ÿคธโ€โ™‚๏ธNaming activities
      • โœ๏ธTracking time in your Journal
      • โฒ๏ธSend your first timesheet
    • ๐Ÿ“ฑTracking time via WhatsApp
    • ๐Ÿ–ฅ๏ธFor Approvers
      • ๐Ÿ’ฌApproving timesheets via WhatsApp
  • Troubleshooting
    • ๐Ÿ”€Tangled Identities
Powered by GitBook
On this page
  • Creating a new collection
  • Edit, design and configure
  • Open
  • Close and force close
  1. Zipwire Collect

Lifecycle of a Collection

Here we explain how a collection comes into the world, exists for a while and then gets closed.

Creating a new collection

A collection starts with the person who you're collecting documents from, otherwise known as the respondent.

  • Head to My docs and then go to the Create tab and stick their email address in. Or, if you have already collected from them...

  • Go to the Our people section and find the person you'd like to collect documents from, hit Manage and then hit the Collect documents button

If the email address is unknown to Zipwire, we'll send an invitation out, otherwise we'll locate their account and take you to the Create tab of their documents section where you can name the collection, pick a template (if you have any saved), and get going.

Edit, design and configure

Once created, you'll see the collection in its editing state. The respondent has not yet been notified, so you're safe to delete it again and they'll be none the wiser.

In this mode, you can add and remove documents and packs and get it how you want it. Once you think it's all good, click Open. This'll take a few moments and during this time we'll email and send WhatsApp messages to your respondent.

Open

Once open, your respondent can see it in their Open tab and they can (and should) send you documents for review.

What the Respondent Sees at Their End

You can make some documents optional and you can upload your own files, for example if you find copies somewhere or they send them to you some other way.

Other than that, you generally wait. Zipwire Collect will remind your respondent if they stop sending you things.

You can see if someone has logged-in to Zipwire by visiting Our people and click Manage where you'll see an overview of them.

This view captures your workplace's relationship with this person.

Close and force close

Once everything has arrived and you're happy, you can and should close the collection. We'll let your respondent know and thank them.

Your respondent can also hit the Force close button on their side. This marks all remaining documents as refused and closes the collection so they won't get nagged again.

Closed collections pile up under the Done tab. At present there is no archive. You can come here to see past collections and access their files and view their forms.

PreviousWhat the Respondent Sees at Their EndNextBulk Upload

Last updated 11 months ago

โ™ป๏ธ
The Force close button on the respondent's side