From 48f1ea994b581ad2a712146e149fdd9921c18ed8 Mon Sep 17 00:00:00 2001 From: Will Mayhone <51935532+willmayhone88@users.noreply.github.com> Date: Tue, 27 Feb 2024 22:50:45 -0600 Subject: [PATCH] Update pricing-features-table.yml (#16739) Added a customer quote to the human endpoint mapping # 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 permissions changes (docs/Using Fleet/manage-access.md) - [ ] 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 - [ ] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [ ] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [ ] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [ ] 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)). --------- Co-authored-by: Mike McNeil --- handbook/company/pricing-features-table.yml | 3 +++ 1 file changed, 3 insertions(+) diff --git a/handbook/company/pricing-features-table.yml b/handbook/company/pricing-features-table.yml index e618ee79e2..21d7d3cecb 100644 --- a/handbook/company/pricing-features-table.yml +++ b/handbook/company/pricing-features-table.yml @@ -123,6 +123,9 @@ demos: - description: Security engineers at a top gaming company wanted to get demographics off their macOS, Windows, and Linux machines about who the user is and who's logged in. moreInfoUrl: https://docs.google.com/document/d/1qFYtMoKh3zyERLhbErJOEOo2me6Bc7KOOkjKn482Sqc/edit + - description: Data engineers at a top biotech corporation needed to know who is logged into their devices. + quote: So we don't know exactly what's going on after we deploy the device, we know that they are compliant with the security because we are running these stuff, but we don't know certainly who is running, who is logging in the device? + moreInfoUrl: https://docs.google.com/document/d/17MNI5ykzlFjdVmQ8SPMrT1oR_hY_vkYAJx31F7l7Pv8/edit#heading=h.7en766pueek4 waysToUse: - description: Look up computer by ActiveDirectory account - description: Find device by Google Chrome user