empayre/fleet
14
0
Fork 0
mirror of https://github.com/empayre/fleet.git synced 2024-11-06 08:55:24 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Maximum allowable adjustments to standard contract terms (#10241)

Browse Source 
# Checklist for submitter

If some of the following don't apply, delete the relevant line.

- [ ] Changes file added for user-visible changes in `changes/` or
`orbit/changes/`.
See [Changes
files](https://fleetdm.com/docs/contributing/committing-changes#changes-files)
for more information.
- [ ] Documented any API changes (docs/Using-Fleet/REST-API.md or
docs/Contributing/API-for-contributors.md)
- [ ] Documented any permissions changes
- [ ] Input data is properly validated, `SELECT *` is avoided, SQL
injection is prevented (using placeholders for values in statements)
- [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for
new osquery data ingestion features.
- [ ] Added/updated tests
- [ ] Manual QA for all new/changed functionality
  - For Orbit and Fleet Desktop changes:
- [ ] Manual QA must be performed in the three main OSs, macOS, Windows
and Linux.
- [ ] Auto-update manual QA, from released version of component to new
version (see [tools/tuf/test](../tools/tuf/test/README.md)).
This commit is contained in:
Mike McNeil 2023-03-01 21:03:58 -06:00 committed by GitHub
parent 2ed2940683
commit b016c5546a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
handbook/customers/README.md
View File

@ -288,6 +288,11 @@ Fleet's subscription agreement is available at [fleetdm.com/terms](https://fleet
Fleeties can find a summary of contract terms in the relevant [customer's Salesforce opportunity.](https://fleetdm.lightning.force.com/lightning/o/Opportunity/list?filterName=Recent)
### Standard terms
For all subscription agreements, NDAs, and similar contracts, Fleet maintains a [standard set of terms and maximum allowable adjustments for those terms](https://docs.google.com/spreadsheets/d/1gAenC948YWG2NwcaVHleUvX0LzS8suyMFpjaBqxHQNg/edit#gid=1136345578).
Exceptions to these maximum allowable adjustments always require CEO approval, whether in the form of redlines to Fleet's agreements or in terms on a prospective customer's own contract.
### Reviewing subscription agreement
To quickly get help doing a legal review of a prospect subscription agreement, with or without redlines:
@ -297,11 +302,11 @@ To quickly get help doing a legal review of a prospect subscription agreement, w
3. Follow the instructions in the "Submitting this request" section
If the prospect/customer/partner is originating the request for signature:
1. Communicate that the Fleet signatory is Mike McNeil, CEO and share his email
1. Communicate to the prospect that the Fleet signatory is Mike McNeil, CEO and share his email.
2. Mike will create the github issue mentioned above when he gets request
3. Mike will forward to business operations for review
4. Business operations will notify Mike and internal requestor when ready for signature
5. Mike will sign and close the issue
4. Business operations will notify Mike and the requestor (via GitHub comment w/ at-mention) when ready for signature
5. Mike will sign and close the issue. (This sends a notification to the requestor automatically.)
## Customer DRI change
Sometimes there is a change in the champion within the customer's organization.