You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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 :)
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
platform.hellosign@
forwarder to @hyphacoop/business-planning-wgThe text was updated successfully, but these errors were encountered: