Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 46

Creating a consulting agreement (#5273)

Browse source 
DocuSign steps for consulting agreement
This commit is contained in:
Charlie Chance 2022-04-21 08:46:30 -06:00 committed by GitHub
parent 1aff4a4231
commit 1b2b68049e
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
handbook/people.md
View file

@ -287,6 +287,12 @@ Once the agreement is sent, add a new row to the [advisory board spreadsheet](ht
When the agreement is completed, make sure it is in the correct Google Drive folder, and ask the new
advisor to add us on [Linkedin](https://www.linkedin.com/company/71111416), [Crunchbase](https://www.crunchbase.com/organization/fleet-device-management) and [Angellist](https://angel.co/company/fleetdm).
## Onboarding a new consultant
Consultant agreements are sent through [Docusign](https://www.docusign.com/), using the "Consulting Agreement" template. To send a new consulting agreement, you'll need the new consultant's name, the term of the service, a summary of the services provided and the consultant's fee.
Then hit send! After all signatures are there, it will automatically be uploaded to the appropriate Google Drive folder by our automation, and a Slack message will appear in the `#g-people` channel.
## Zapier and DocuSign
We use Zapier to automate how completed DocuSign envelopes are formatted and stored. This process ensures we store signed documents in the correct folder and that filenames are formatted consistently.