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
        • Potential for Sleeper Wallets on Ethereum
  • 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
  1. Zipwire Approve

Logical structure

Here's how Zipwire organises its key concepts.

PreviousPayment MethodsNextSet up your workplace

Last updated 1 year ago

Structure

Your workplace and its clients

The in Zipwire represents the business or organization that manages everyone, assigns work to workers and creates teams of approvers and processors.

The workplace has an Administrators Team and its members have full rights over the workplace.

In more unusual cases, a user may be an administrator of more than one workplace. If so, additional UI controls will appear to allow that user to switch between the workplace they're acting upon.

As in real life, the workplace can (and likely does) have many clients, and each client can have many assignments.

Assignments and teams

The is a collection of settings about what the name of the assignment is and who the senders are, and who will approve and process their timesheets.

When you go first setup your workplace, you'll be taken through some steps to create your first assignment. This will also create two new for its approvers and processors–each time you create a new assignment, Zipwire will create two new teams.

The teams are actually independent of the assignments and are logically just children of the workplace.

This means you can use the same team to approve or process many assignments. If you're a staffing agency, you may want a single team for all the people who process timesheets, and you can do this.

It's possible to switch the entire team that does the processing (or approving) on an assignment.

Teams can be renamed anytime, or deleted, once it has no assignments and no members.

Organizing with assignments

You can use however you wish to break up groups of senders, approvers and processors.

Usually it's the approvers that determine when to make another assignment, just as in a company, it's the line managers that lead groups of people.

In general, people tend to work under a line manager who may have a deputy. These people would approve people's timesheets and so they would have an assignment for their team, and that would have a Zipwire team holding the line manager and her deputy.

Another reason to create or even split an assignment up is because of different configuration. This is rare because each sender can have their own , and each rate can have its own .

πŸ”²
workplace
assignment
teams
assignments
rate plan
billing plan