From 0fde0ef9b703153ffcae698815fa9cd48f0d5be5 Mon Sep 17 00:00:00 2001 From: Tina Ong Date: Tue, 11 Nov 2025 18:12:14 -0800 Subject: [PATCH] Update communications.md (#35582) **Related issue:** Resolves # # Checklist for submitter If some of the following don't apply, delete the relevant line. - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes ## Testing - [ ] Added/updated automated tests - [ ] Where appropriate, [automated tests simulate multiple hosts and test for host isolation](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/reference/patterns-backend.md#unit-testing) (updates to one hosts's records do not affect another) - [ ] QA'd all new/changed functionality manually For unreleased bug fixes in a release candidate, one of: - [ ] Confirmed that the fix is not expected to adversely impact load test results - [ ] Alerted the release DRI if additional load testing is needed ## 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. - [ ] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). ## New Fleet configuration settings - [ ] Setting(s) is/are explicitly excluded from GitOps If you didn't check the box above, follow this checklist for GitOps-enabled settings: - [ ] Verified that the setting is exported via `fleetctl generate-gitops` - [ ] Verified the setting is documented in a separate PR to [the GitOps documentation](https://github.com/fleetdm/fleet/blob/main/docs/Configuration/yaml-files.md#L485) - [ ] Verified that the setting is cleared on the server if it is not supplied in a YAML file (or that it is documented as being optional) - [ ] Verified that any relevant UI is disabled when GitOps mode is enabled ## fleetd/orbit/Fleet Desktop - [ ] Verified compatibility with the latest released version of Fleet (see [Must rule](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/workflows/fleetd-development-and-release-strategy.md)) - [ ] If the change applies to only one platform, confirmed that `runtime.GOOS` is used as needed to isolate changes - [ ] Verified that fleetd runs on macOS, Linux and Windows - [ ] Verified auto-update works from the released version of component to the new version (see [tools/tuf/test](../tools/tuf/test/README.md)) --------- Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com> --- handbook/company/communications.md | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-) diff --git a/handbook/company/communications.md b/handbook/company/communications.md index ef5b93b4bd..eec766f052 100644 --- a/handbook/company/communications.md +++ b/handbook/company/communications.md @@ -614,6 +614,26 @@ In brief, this means that as a Fleet team member, you may: For more developed thoughts about __spending guidelines and limits__, please read [GitLab's open expense policy](https://about.gitlab.com/handbook/finance/spending-company-money/). +### Paying back company money + +If you have accidentally incurred a charge on your Brex card that was not intended and/or approved, you can initiate a "Repay" process in Brex that would allow you to pay back the company. + +1. Login to [brex.com](http://brex.com/) with your Fleet email and navigate to the "[Wallet](https://dashboard.brex.com/wallet)". +2. Select the transaction you'd like to repay. + +> If you need to split the transaction amount: +> - Ensure the transaction is in the "Approved" status. If it's not in "Approved" status yet, wait a few days and retry. +> - Click "Itemize this expense." +> - Separate out the amount that needs to be repaid. +> - Click "Itemize" and proceed to the next step. + +3. On the bottom right-hand side, click on "Repay". +4. Select the desired bank account and verify the account. +5. Click "confirm repayment". + +After a short period of processing, your transaction will show as “denied”, and this means the repayment is in process. + + ## Travel When attending a conference or traveling for Fleet, keep the following in mind: @@ -666,18 +686,14 @@ Finance will review and process your request within 2 business days. ### Attending conferences -The Marketing department is responsible for executing and organizing all [marketing-related events](https://fleetdm.com/handbook/marketing#settle-event-strategy). When attending a conference for Fleet, treat it [like other travel for the company](https://fleetdm.com/handbook/company/communications#travel). - -The relevant department head should approve and organize all other event types (trainings, developer conferences, meetups, etc.). +The Marketing department is responsible for executing and organizing all [marketing-related events](https://fleetdm.com/handbook/marketing#settle-event-strategy). When attending a conference for Fleet, treat it [like other travel for the company](https://fleetdm.com/handbook/company/communications#travel). The relevant department head should approve and organize all other event types (trainings, developer conferences, meetups, etc.). image ### Offsites -From time to time, Fleet organizes offsites to bring team members together in person. This encourages trust and makes the company more productive. - -Offsites are: +From time to time, Fleet organizes offsites to bring team members together in person. This encourages trust and makes the company more productive. Offsites are: - Attended by a particular [product group](https://fleetdm.com/handbook/company#product-groups), a [department](https://fleetdm.com/handbook/company#org-chart), or a team such as the E-group. - Sometimes also attended by founders or other team members on a case-by-case basis. - 1-3 full days long (2-4 nights stay).