Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set up external doc-signing tool #195

Closed
10 tasks done
patcon opened this issue Jan 30, 2020 · 4 comments
Closed
10 tasks done

Set up external doc-signing tool #195

patcon opened this issue Jan 30, 2020 · 4 comments
Assignees
Labels
operations Back office operations tasks opportunities Back office opportunities tasks

Comments

@patcon
Copy link
Contributor

patcon commented Jan 30, 2020

This initial comment is collaborative and open to modification by all.

Task Summary

🎟️ Re-ticketed from: https://github.com/hyphacoop/organizing-private/issues/13
πŸ—£ Loomio: N/A
πŸ“… Due date: N/A
🎯 Success criteria: We've signed the first doc and shared thoughts on experience here.

We already have an internal signing process using PGP/Keybase (which we used for org resolutions hyphacoop/handbook#21), but we should have a simpler one for external clients.

To Do

  • try a tool with personal email: HelloSign -- patcon
  • send first doc to client -- patcon
  • share feedback on how it went (see below)
  • document how it worked in this issue
  • ask for consent to migrate account to org ownership
  • transfer account to org
    • create platform.hellosign@ forwarder to @hyphacoop/business-planning-wg
    • adjust profile to be general for org
    • store in /passwords
    • add to /inventory
@patcon patcon added opportunities Back office opportunities tasks operations Back office operations tasks labels Jan 30, 2020
@patcon patcon self-assigned this Jan 30, 2020
@patcon
Copy link
Contributor Author

patcon commented Jan 30, 2020

From chat convo:

  • πŸ’‘ can convert patcon's personal hellosign account into org account (patcon)
  • πŸ’‘ we could use Adobe's desktop software for signing (ben)
    • πŸ” signers can sometimes sign in such a way that they edit document and corrupt it (yurko)
    • ❀️ hellosign flow was really smooth and simple (patcon)
    • πŸ” docusign can cost $30K for some orgs (yurko's)
      • ❀️ nice that hellosign is free (yurko)
  • βœ… decision: make hellosign account available, and others use it at will (patcon) πŸ‘ ben, yurko
  • πŸ” HelloSign offers 3 free doc-signings per month
    • πŸ’‘ if we go over, we can either use another personal account (outside our shared history) or upgrade to USD$15/mo plan (unlimited)

@patcon
Copy link
Contributor Author

patcon commented Jan 30, 2020

How I used HelloSign:
Screencast: https://recordit.co/X8whEde5IH (mp4)

  1. Sign in (see passbolt)
  2. For "Who needs to sign?" choose "Just Others"
  3. Upload the file (doesn't count to quota until sent)
  4. Add all signers, including Hypha's rep first
  5. Click "Assign signer order" to enforce order.
  6. Click "Prepare docs for signing" to place/assign the fields.
  7. Give the agreement a nice, human readable title, and nice message.
  8. Send it along! (This will initiate sending, and use up 1 doc from our monthly quota)

@patcon
Copy link
Contributor Author

patcon commented Jan 30, 2020

How it went:

  • HelloSign sends updates (to account owner, now business planning WG) whenever the doc moves through a step of the pipeline to completion, e.g., as each sequential recipient either views and/or signs their section.
  • Every signer automatically gets a copy with audit trail.
  • signers have many options to sign, including upload of signature image (which this actual client used), typing, drawing with trackpad, or sending to touchscreen mobile device for finger sig.

@patcon
Copy link
Contributor Author

patcon commented Jan 30, 2020

We can move some of this into handbook when someone else uses it and validates that it's something we should keep doing. Seems out of scope for now, so we can just mark this as done and revisit :)

@dcwalk dcwalk closed this as completed Feb 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
operations Back office operations tasks opportunities Back office opportunities tasks
Projects
No open projects
Development

No branches or pull requests

2 participants