From 55c207ff58f8adc53fb2c90c3123804f3c3ddba7 Mon Sep 17 00:00:00 2001 From: Nathanael Holliday <100959072+hollidayn@users.noreply.github.com> Date: Tue, 6 Feb 2024 18:47:18 -0600 Subject: [PATCH] Updating the "updating personnel details section" (#16525) Adding steps to look at when someone is changing their place of residence. # 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)). --- handbook/business-operations/README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/handbook/business-operations/README.md b/handbook/business-operations/README.md index d10dfd6657..6b31ff3141 100644 --- a/handbook/business-operations/README.md +++ b/handbook/business-operations/README.md @@ -142,6 +142,7 @@ When a Fleetie, consultant or advisor requests an update to their personnel deta - Note: if making the change requires follow up steps, resolve those steps to action the change. - Once change is effected in HRIS, BizOps makes changes to ["πŸ§‘β€πŸš€ Fleeties"](https://docs.google.com/spreadsheets/d/1OSLn-ZCbGSjPusHPiR5dwQhheH1K8-xqyZdsOe9y7qc/edit#gid=0) spreadsheet. - If required, BizOps makes any relevant changes to [Fleet's equity plan](https://docs.google.com/spreadsheets/d/1_GJlqnWWIQBiZFOoyl9YbTr72bg5qdSSp4O3kuKm1Jc/edit#gid=0). +- If required, BizOps makes any relevant changes to the ["πŸ—ΊοΈ Geographical factors"](https://docs.google.com/spreadsheets/d/1rCVCs-eOo-VSEG7fPLgdq5l7oSaActl5bewaWP7PnSE/edit#gid=1533353559) spreadsheet and follows through on any action items involving tax implications (i.e. registering with a new state for employer taxes). - If required, BizOps also makes changes to other core systems (e.g: creating a new email alias in google workspace; updating details in Carta; etc). - The change is now actioned, notify the team member and close the issue.