Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-04-21 13:37:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 91

Handbook: org and responsibilities update (#38527)

Browse source 
Co-authored-by: Sam Pfluger <108141731+Sampfluger88@users.noreply.github.com>
This commit is contained in:
Isabell Reedy 2026-01-21 00:20:16 +00:00 committed by GitHub
parent 48df078026
commit fcac359298
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
24 changed files with 263 additions and 273 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
CODEOWNERS
View file

@ -122,11 +122,11 @@ go.mod @fleetdm/go
/handbook/company/open-positions.yml @ireedy
#/handbook/company/product-groups.md Covered in custom.js
/handbook/company/go-to-market-groups.md @sampfluger88
/handbook/finance/security.md @allenhouchins # TODO move these files to `it-and-enablement/`
#/handbook/finance/README.md Covered in custom.js
#/handbook/finance/finance.rituals.yml Covered in custom.js
#/handbook/people Covered in custom.js
#/handbook/it-and-enablement Covered in custom.js
#/handbook/it Covered in custom.js
/handbook/it/security.md @allenhouchins
#/handbook/customer-success Covered in custom.js
#/handbook/marketing Covered in custom.js
#/handbook/sales Covered in custom.js

2
articles/tales-from-fleet-security-soc2.md
View file

@ -43,7 +43,7 @@ One of the essential things about SOC 2 is having the right security policies. T
Writing policies from scratch can seem daunting. Many compliance automation products have templates you can use to get started, but there are excellent free and open resources online.
As you can see, our policies are in our [handbook](https://fleetdm.com/handbook/finance/security#information-security-policy-and-acceptable-use-policy), and we created most of them using this [free set of templates](https://github.com/JupiterOne/security-policy-templates) published by JupiterOne under Creative Commons licensing.
As you can see, our policies are in our [handbook](https://fleetdm.com/handbook/it/security#information-security-policy-and-acceptable-use-policy), and we created most of them using this [free set of templates](https://github.com/JupiterOne/security-policy-templates) published by JupiterOne under Creative Commons licensing.
We kept our policies as basic as possible to make sure everything in them is valuable and achievable. Having policies that state you must do the impossible is a surefire way of getting in trouble! The templates we used contained many processes and procedures as well. We used the policies and will eventually document more of our procedures in our handbook.

2
handbook/ceo/README.md
View file

@ -20,7 +20,7 @@ This page details processes specific to working [with](#contact-us) and [within]
Ultimately, the CEO is responsible for the success or failure of the company. The CEO is the [directly responsible individual (DRI)](https://fleetdm.com/handbook/company/why-this-way#why-direct-responsibility) for pricing tiers, the business model, human resources, legal counsel, signatures on all documents, and brand &amp; product marketing (brandfronts, pitchfronts, featurefronts, ICPs, personas, and targeting).
> **Note:** When the CEO is out of office, CEO responsibilities are either paused, delegated, or coordinated through the [Head of Digital Workplace & GTM Systems](https://fleetdm.com/handbook/it-and-enablement#team) so they can be handled promptly. (It depends on the responsibility and the situation.)
> **Note:** When the CEO is out of office, CEO responsibilities are either paused, delegated, or coordinated through the [GTM Systems Architect](https://fleetdm.com/handbook/finance#team) so they can be handled promptly. (It depends on the responsibility and the situation.)
### Process the CEO's inbox

8
handbook/company/README.md
View file

@ -142,12 +142,12 @@ To provide clarity about decision-making, [responsibility](https://fleetdm.com/h
- 🚀 [Engineering](https://fleetdm.com/handbook/engineering): The Engineering department at Fleet is directly responsible for writing and maintaining the code for Fleet's core product, as well as Fleet's Information technology (IT) infrastructure.
- 🦢 [Product Design](https://fleetdm.com/handbook/product-design): The Product Design department is directly responsible for defining and prioritizing the changes made to the core product, Fleet API, and reference documentation.
- 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement): The IT & Enablement department is directly responsible for solutions consulting, customer training curriculum, prospect enablement, and dogfooding, as well as the framework, schema, equipment, internal tooling, automation, and technology behind Fleet's Go-To-Market (GTM) systems, remote work, the handbook, issue templates, Zapier flows, Docusign templates, key spreadsheets, and project management tools.
- 🌐 [IT](https://fleetdm.com/handbook/it): The IT department is directly responsible Fleet's internal IT/Security policies, solutions consulting, and dogfooding Fleet the product.
- 🌦️ [Customer Success](https://fleetdm.com/handbook/customer-success): The customer success department is directly responsible for ensuring that customers and community members of Fleet achieve their desired outcomes with Fleet products and services.
- 🐋 [Sales](https://fleetdm.com/handbook/sales): The Sales department is directly responsible for attaining the revenue goals of Fleet and helping customers deliver on their objectives.
- 🫧 [Marketing](https://fleetdm.com/handbook/marketing): The Marketing department is directly responsible for growing awareness of Fleet and nurturing the community through participation in events, conversations, and other programs.
- 💸 [Finance](https://fleetdm.com/handbook/finance): The Finance department is directly responsible for accounts receivable including invoicing, accounts payable including commision calculations, expense reporting including Brex memos and maintaining accurate spend projections in "🧮The numbers", sales taxes, payroll taxes, corporate income/franchise taxes, and financial operations including bank accounts and cash flow management.
- 🧑‍🚀 [People](https://fleetdm.com/handbook/people): The People department is directly responsible for Fleet's culture, human resources, benefits, recruiting, workiversaries, opening positions, compensation planning, onboarding, and offboarding.
- 🫧 [Marketing](https://fleetdm.com/handbook/marketing): The Marketing department is directly responsible for growing awareness of Fleet, customer training curriculum, and prospect enablement, and nurturing the community through participation in events, conversations, and other programs.
- 💸 [Finance](https://fleetdm.com/handbook/finance): The Finance department is directly responsible for accounts receivable including invoicing, accounts payable including commision calculations, compliance, expense reporting including Brex memos and maintaining accurate spend projections in "🧮The numbers", sales taxes, payroll taxes, corporate income/franchise taxes, financial operations including bank accounts and cash flow management, Zapier flows, as well the internal tooling, automation, and technology behind Fleet's Go-To-Market (GTM) systems.
- 🧑‍🚀 [People](https://fleetdm.com/handbook/people): The People department is directly responsible for Fleet's culture, human resources, benefits, opening positions, compensation planning, onboarding, offboarding, remote work, the handbook, issue templates, Docusign templates, key spreadsheets, and project management tools.
## Advisors

48
handbook/company/communications.md
View file

@ -11,7 +11,7 @@ All team members should attend the "All hands" every month. "All hands" meeting
### E-group
Every week, the "Executive" or "E-group", including the CEO, CTO, Head of Product Design, CRO, CFO, VP of Customer Success, and Head of Digital Workplace & GTM Systems, will hold a 30-minute "¶ 🗣 Roundup (E-Group)" meeting to discuss the company's immediate needs and address any blockers.
Every week, the "Executive" or "E-group", including the CEO, CTO, Head of Product Design, CRO, CFO, VP of Customer Success, will hold a 30-minute "¶ 🗣 Roundup (E-Group)" meeting to discuss the company's immediate needs and address any blockers.
Every three weeks, the E-group will meet for a more in-depth discussion immediately following the "¶ 🗣 Roundup (E-Group)" meeting, regarding the achievement of strategic short and long-term company goals. This is the "¶ 🗣 E-Group review" meeting, typically held from 3-5pm CT. If one of the department heads cannot attend this meeting, the Executive Assistant will reschedule the E-group review as close to the original time as possible, while verifying that all E-group members can attend.
@ -35,7 +35,7 @@ The ambition of Fleet's product roadmap is to reach [product maturity](http://fl
## Security
Security policies are best when they're alive, in context of how an organization operates. Fleeties [follow onboarding and offboarding SLAs](https://fleetdm.com/handbook/finance/security#human-resources-security-policy), [carry Yubikeys](https://fleetdm.com/handbook/finance/security#hardware-security-keys), use a password manager (even for [personal devices](https://fleetdm.com/handbook/finance/security#personal-mobile-devices)), implement change control of [policies](https://fleetdm.com/handbook/finance/security#security-policies), [recover their accounts via strict processes](https://fleetdm.com/handbook/finance/security#account-recovery-process), and access control is driven primarily through GitOps and SSO.
Security policies are best when they're alive, in context of how an organization operates. Fleeties [follow onboarding and offboarding SLAs](https://fleetdm.com/handbook/it/security#human-resources-security-policy), [carry Yubikeys](https://fleetdm.com/handbook/it/security#hardware-security-keys), use a password manager (even for [personal devices](https://fleetdm.com/handbook/it/security#personal-mobile-devices)), implement change control of [policies](https://fleetdm.com/handbook/it/security#security-policies), [recover their accounts via strict processes](https://fleetdm.com/handbook/it/security#account-recovery-process), and access control is driven primarily through GitOps and SSO.
### Trust
@ -67,8 +67,8 @@ Fleet is successful because of our customers and community, and those relationsh
| Release article | <sup><sub>_See [🦢 Head of Product Design](https://fleetdm.com/handbook/product-design#team)_</sup></sub>
| Onboarding and training | <sup><sub>_See [🧑‍🚀 Head of People](https://fleetdm.com/handbook/people#team)_</sup></sub>
| Payroll and benefits | <sup><sub>_See [🧑‍🚀 Head of People](https://fleetdm.com/handbook/people#team)_</sup></sub>
| Information technology (IT) | <sup><sub>_See [🌐 IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#team)_</sup></sub>
| Internal tools & equipment | <sup><sub>_See [🌐 IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#team)_</sup></sub>
| Information technology (IT) | <sup><sub>_See [🌐 IT & Enablement](https://fleetdm.com/handbook/it#team)_</sup></sub>
| Internal tools & equipment | <sup><sub>_See [🌐 IT & Enablement](https://fleetdm.com/handbook/it#team)_</sup></sub>
| Bookkeeping, AR/AP | <sup><sub>_See [💸 Finance](https://fleetdm.com/handbook/finance#team)_</sup></sub>
| Legal contracts | <sup><sub>_See [💸 Finance](https://fleetdm.com/handbook/finance#team)_</sup></sub>
| Customer renewals | <sup><sub>_See [🌦️ VP of Customer Success](https://fleetdm.com/handbook/customer-success#team)_</sup></sub>
@ -89,7 +89,7 @@ Fleet is successful because of our customers and community, and those relationsh
| What goes in a release (Release DRI) | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
| Engineering output and architecture | <sup><sub>_See [🚀 Chief Technology Officer](https://fleetdm.com/handbook/engineering#team)_ </sup></sub>
| Product development | <sup><sub>_See [🛩️ Product groups](https://fleetdm.com/handbook/company/product-groups#current-product-groups)_ </sup></sub>
| Fleet-maintained apps | <sup><sub>_[Allen Houchins](https://fleetdm.com/handbook/it-and-enablement#team)_</sup></sub>
| Fleet-maintained apps | <sup><sub>_[Allen Houchins](https://fleetdm.com/handbook/it#team)_</sup></sub>
@ -116,7 +116,7 @@ Fleet is successful because of our customers and community, and those relationsh
> ***Zoom***
> We use [Zoom](https://zoom.us) for virtual meetings at Fleet, and it is important that every team member feels comfortable hosting, joining, and scheduling Zoom meetings. By default, some settings have been intentionally locked and can't be changed, but others can be adjusted on your [profile settings](https://zoom.us/profile/setting) page.
>
> Need help with Zoom? Reach out to 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us).
> Need help with Zoom? Reach out to 🌐 [IT](https://fleetdm.com/handbook/it#contact-us).
### Recording meetings
@ -127,11 +127,11 @@ Capturing video from meetings with customers, prospects, and community members o
- If the call has external participants and is recorded, this call is stored in Gong for future use.
To access a recording saved in Gong, visit [app.gong.io](https://app.gong.io) and sign in with SSO.
- Everyone at Fleet has access, whether they have a Gong seat or not, and you can explore and search through any uploaded call transcripts unless someone marks them as private (though the best practice would be not to record any calls you don't want to be captured).
If you ever make a mistake and need to delete something, you can delete the video in Gong or reach out to 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us) for help. They will delete it immediately without watching the video.
If you ever make a mistake and need to delete something, you can delete the video in Gong or reach out to 🌐 [IT](https://fleetdm.com/handbook/it#contact-us) for help. They will delete it immediately without watching the video.
- Note that any recording stopped within 60 seconds of the start of the recording is not saved in Gong, and there will be no saved record of it.
Most folks at Fleet should see no difference in their meetings if they aren't interfacing with external parties.
Our goal in using Gong and recording calls is to capture insights from sales, customer, and community meetings and improve how we position and sell our product. We never intend to make anyone uncomfortable, and we hope you reach out to our DRI for Gong, 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us) if you have questions or concerns.
Our goal in using Gong and recording calls is to capture insights from sales, customer, and community meetings and improve how we position and sell our product. We never intend to make anyone uncomfortable, and we hope you reach out to our DRI for Gong, 🌐 [IT](https://fleetdm.com/handbook/it#contact-us) if you have questions or concerns.
> ***Excluding calls from being recorded***
@ -170,7 +170,7 @@ Our Zoom meetings are configured to let participants join before the host arrive
**External meetings**: When scheduling external meetings, provide external participants with a
[Calendly](https://calendly.com) link to schedule with the relevant internal participants.
> Need a Calendly account? Reach out to 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us).
> Need a Calendly account? Reach out to 🌐 [IT](https://fleetdm.com/handbook/it#contact-us).
It is important to [set your working hours](https://support.google.com/calendar/answer/7638168?hl=en&co=GENIE.Platform%3DDesktop) in Google Calendar and block out any personal time/events/PTO, so that team members do not inadvertently schedule a time when you are not available. Many team members use the free tier of [reclaim.ai](https://reclaim.ai/) to synchronize personal event times (without event details) into their work calendars.
@ -182,7 +182,7 @@ It is also common practice to block out time for focused work. In an all-remote
["**No agenda, no attenda**."](https://about.gitlab.com/company/culture/all-remote/live-doc-meetings/#gitlab-meeting-best-practices) Every work-related meeting should have an editable agenda (e.g. edit access shared with all attendees) attached to the calendar invite.
- To create a meeting agenda please make a copy of [Fleet's meeting template](https://docs.google.com/document/d/1TaZ654gTwadWGDYhP3zuAzWe0eiY0s9NhaU9KLCokgw/copy).
> Tired of making agendas manually? Ask the 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us) about our [meeting notes automation](https://fleetdm.zoom.us/clips/share/Gd69AuhMSqGIN7NE8JxPvA). Please do not use Google Calendar's automatic agenda/notes creation function, as it does not adhere to Fleet's preferred agenda format. If the automatic agenda doc has been created in error, edit the calendar invite to delete it from the meeting to avoid confusion.
> Tired of making agendas manually? Ask the 💸 [GTM Systems Architect](https://fleetdm.com/handbook/finance#contact-us) about our [meeting notes automation](https://fleetdm.zoom.us/clips/share/Gd69AuhMSqGIN7NE8JxPvA). Please do not use Google Calendar's automatic agenda/notes creation function, as it does not adhere to Fleet's preferred agenda format. If the automatic agenda doc has been created in error, edit the calendar invite to delete it from the meeting to avoid confusion.
### Modifying an event organized by someone else
@ -194,7 +194,7 @@ This works because every Fleetie grants edit access to everyone else at Fleet as
### Shared calendars
Team calendars are the primary source for sprint rituals; they facilitate the execution of each sprint.
Looking to add, change, or remove a shared calendar? [Create an issue](https://fleetdm.com/handbook/it-and-enablement#contact-us) and the appropriate DRI will reply with feedback.
Looking to add, change, or remove a shared calendar? [Create an issue](https://fleetdm.com/handbook/people#contact-us) and the appropriate DRI will reply with feedback.
### 1:1 meetings
@ -227,7 +227,7 @@ There are [several special email addresses](https://docs.google.com/document/d/1
Fleet uses these levels to standardize a commitment to minimal esotericism across the company.
- **Public:** _Share with anyone, anywhere in the world_
- **Confidential:** _Share only with team members who've signed an NDA, consulting agreement, or employment agreement_
- **Classified:** _Share only with the CEO, Executive Assistant, Head of People, Head of Digital Workplace & GTM Systems, and/or the people involved. e.g., US social security numbers during hiring_
- **Classified:** _Share only with the CEO, Executive Assistant, Head of People, GTM Systems Architect, and/or the people involved. e.g., US social security numbers during hiring_
### Document titles
@ -236,7 +236,7 @@ Fleet uses these levels to standardize a commitment to minimal esotericism acros
- **"Public":** _(Available to public)_
- _(Confidential - for Fleet eyes only)_
- **"¶":** _(E-group - Direct reports the the CEO)_
- **"¶¶":** _(Classified - CEO, Executive Assistant, Head of People, and Head of Digital Workplace & GTM Systems)_
- **"¶¶":** _(Classified - CEO, Executive Assistant, Head of People, and GTM Systems Architect)_
## Company database
@ -255,7 +255,7 @@ At Fleet, we do not send internal emails to each other. Instead, we prefer to us
- In consideration of our team, Fleet avoids using global tags in channels (i.e. @here, @channel, etc.) (What about polls? Good question, Fleeties are asked to post their poll in the channel and @mention the teammates they would like to hear from.)
- To save everyone time, please [don't ask to ask: just ask](https://dontasktoask.com/).
> **Need an app that you don't see in Fleet Slack?** [Create a IT & Enablement issue](https://fleetdm.com/handbook/it-and-enablement#contact-us) to request an app be added to the Fleet Slack workspace.
> **Need an app that you don't see in Fleet Slack?** [Create a IT issue](https://fleetdm.com/handbook/it#contact-us) to request an app be added to the Fleet Slack workspace.
### Key Slack channels
@ -290,7 +290,7 @@ Any change to fleetdm.com follows the same process as [making changes](https://f
Before committing anything to code, we create wireframes (referred to as ["drafting"](https://fleetdm.com/handbook/company/product-groups#making-changes)) to illustrate all changes that affect the layout and structure of the user interface, design, or APIs of fleetdm.com. See [Why do we use a wireframe first approach](https://fleetdm.com/handbook/company/why-this-way#why-do-we-use-a-wireframe-first-approach) for more information.
The [IT & Enablement team](https://fleetdm.com/handbook/it-and-enablement#team) holds regular design review sessions to evaluate, revise, and approve wireframes before moving into production. Design review sessions are hosted by the [Head of Design](https://calendar.google.com/calendar/u/0?cid=bXRob21hc0BmbGVldGRtLmNvbQ) and typically take place daily, late afternoon (CT). Anyone is welcome to join.
The [Product Design](https://fleetdm.com/handbook/product-design#team) holds regular design review sessions to evaluate, revise, and approve wireframes before moving into production. Design review sessions are hosted by the [Head of Design](https://calendar.google.com/calendar/u/0?cid=bXRob21hc0BmbGVldGRtLmNvbQ) and typically take place daily, late afternoon (CT). Anyone is welcome to join.
## Design at Fleet
@ -357,7 +357,7 @@ _**Note:**_ There are only a few "special" labels that are exceptions to this ru
> ***Create an issue from a Slack message***
>
> If you need to track content from a Slack channel (e.g. #help-customers), you can automatically generate a GitHub issue by adding the emoji `create-github-issue` as a reaction to any message. This will automatically:
> - Create an issue tagged with the departmental GitHub label that corresponds with the Slack channel. If there isn't a corresponding departmental label for the channel, the issue defaults to the [#g-it-and-enablement](https://github.com/fleetdm/confidential/issues#workspaces/g-it-and-enablement-6451748b4eb15200131d4bab/board) kanban board.
> - Create an issue tagged with the departmental GitHub label that corresponds with the Slack channel. If there isn't a corresponding departmental label for the channel, the issue defaults to the [:help-it](https://github.com/orgs/fleetdm/projects/101) kanban board.
@ -490,7 +490,7 @@ When attending a conference or traveling for Fleet, keep the following in mind:
- **Tipping:** Tipping norms vary by culture. How you tip when representing the company reflects on Fleet's brand. When traveling in the United States and using your company Brex card, prepare to tip between 18-20% at restaurants. For rideshare, takeout, delivery, and other situations where tipping comes up, tip between 10-20%.
- **Personal credit card:** Please use your personal credit card for hotel incidentals, personal consumables, movies, mini bars, and entertainment. These expenses _will not_ be reimbursed.
- **Company credit card:** We recommend you order a physical Brex card if you do not have one before traveling.
- **Credit card limit increases:** The monthly limit on your Brex card may need to be increased temporarily as necessary to accommodate the increased spending associated with the conference, such as [booking your own travel](https://fleetdm.com/handbook/company/communications#flights). You can [request that here](https://fleetdm.com/handbook/it-and-enablement#contact-us) by providing the following information:
- **Credit card limit increases:** The monthly limit on your Brex card may need to be increased temporarily as necessary to accommodate the increased spending associated with the conference, such as [booking your own travel](https://fleetdm.com/handbook/company/communications#flights). You can [request that here](https://fleetdm.com/handbook/finance#contact-us) by providing the following information:
- The start and end dates for your trip.
- The [price of your flight](https://fleetdm.com/handbook/company/communications#flights)
- The [price of your hotel or Airbnb](https://fleetdm.com/handbook/company/communications#lodging) per night
@ -568,12 +568,12 @@ Your Brex card may be used for up to $500 USD per month in coworking costs. Plea
### Relocating
When Fleeties relocate, there are vendors that need to be notified of the change. Before relocating, please create a [💼 Teammate relocation](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%23g-it-and-enablement&projects=&template=x-teammate-relocation.md) issue to [let the company know in advance](https://fleetdm.com/handbook/it-and-enablement#update-personnel-details) by following the directions listed in the relevant issue template.
When Fleeties relocate, there are vendors that need to be notified of the change. Before relocating, please create a [💼 Teammate relocation](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-people&projects=&template=x-teammate-relocation.md) issue to [let the company know in advance](https://fleetdm.com/handbook/people#update-personnel-details) by following the directions listed in the relevant issue template.
## Tools and equipment
Fleet provides laptops, YubiKey security keys, and software licenses for core team members to use while working at Fleet. If you need new equipment or would like to propose a tool to be used internally at Fleet, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-it-and-enablement%2C%3Ait-gtm&projects=&template=1-custom-request.md&title=) on the 🌐 IT & Enablement kanban board.
Fleet provides laptops, YubiKey security keys, and software licenses for core team members to use while working at Fleet. If you need new equipment or would like to propose a tool to be used internally at Fleet, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-it&projects=&template=1-custom-request.md&title=) on the 🌐 IT kanban board.
### Requesting new equipment
@ -582,7 +582,7 @@ As soon as an offer is accepted, IT & Enablement will reach out to the new team
- **Tracking equipment:** All company-owned devices are tracked in Fleet's ["🍽️ Dogfood" instance](https://dogfood.fleetdm.com/dashboard). When a device is purchased, it's automatically enrolled in dogfood.
- **Returning equipment:** Apple computers with remaining AppleCare Protection Plans should be reprovisioned to other Fleeties who may have older or less-capable computers. Equipment should be returned once offboarded for reprovisioning. Coordinate offboarding and return with the Head of Digital Workplace & GTM Systems. Please return all equipment to the Fleet IT warehouse using Fleet's FedEx account (address and account # in 1Password).
- **Returning equipment:** Apple computers with remaining AppleCare Protection Plans should be reprovisioned to other Fleeties who may have older or less-capable computers. Equipment should be returned once offboarded for reprovisioning. Coordinate offboarding and return with the Head of IT. Please return all equipment to the Fleet IT warehouse using Fleet's FedEx account (address and account # in 1Password).
- **Equipment retention and replacement:** Older equipment results in lost productivity of Fleeties and should be considered for replacement. Replacement candidates are computers that are no longer under an AppleCare+ Protection Plan (or another warranty plan), are >3 years from the [discontinued date](https://everymac.com/systems/apple/macbook_pro/index-macbookpro.html#specs), or when the "Battery condition" status in Fleet is less than "Normal". The old equipment should be evaluated for return or retention as a test environment.
@ -591,7 +591,7 @@ As soon as an offer is accepted, IT & Enablement will reach out to the new team
#### Requesting IT support
If you are in need of IT support, reach out to 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us) to assist with a software or hardware issue. [Open a support request](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-it-and-enablement%2C%3Ait-gtm&projects=&template=1-custom-request.md&title=) and a Fleet IT team member will attempt to correct your issue remotely using Fleet, and will notify you if any action is needed on your part.
If you are in need of IT support, reach out to 🌐 [IT](https://fleetdm.com/handbook/it#contact-us) to assist with a software or hardware issue. [Open a support request](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-it&projects=&template=1-custom-request.md&title=) and a Fleet IT team member will attempt to correct your issue remotely using Fleet, and will notify you if any action is needed on your part.
## Taking time off
@ -660,7 +660,7 @@ Variable compensation (i.e. commission) is reviewed and submitted for processing
#### Compensation changes
Fleet benchmarks US-based team members based on the United States Dollar (USD). Non-US Fleeties are benchmarked in the local currency. Compensation decisions are re-benchmarked yearly, shortly after the anniversary of a team member's start date. The Head of People is responsible for the process to [update compensation](https://fleetdm.com/handbook/it-and-enablement#update-a-team-members-compensation).
Fleet benchmarks US-based team members based on the United States Dollar (USD). Non-US Fleeties are benchmarked in the local currency. Compensation decisions are re-benchmarked yearly, shortly after the anniversary of a team member's start date. The Head of People is responsible for the process to [update compensation](https://fleetdm.com/handbook/people#update-a-team-members-compensation).
#### Exercise stock options
@ -811,10 +811,10 @@ For below, please see 📖[handbook/company/communications#issue-labels](https:/
For above, please see 📖[handbook/company/communications#issue-labels](https://fleetdm.com/handbook/company/communications#issue-labels).
##### Vulnerability monitoring
Please see 📖[handbook/it-and-enablement#check-production-dependencies-of-fleetdm-com](https://fleetdm.com/handbook/it-and-enablement#check-production-dependencies-of-fleetdm-com).
Please see 📖[handbook/engineering#check-production-dependencies-of-fleetdm-com](https://fleetdm.com/handbook/engineering#check-production-dependencies-of-fleetdm-com).
##### Testing changes
Please see 📖[handbook/it-and-enablement#test-fleetdm-com-locally](https://fleetdm.com/handbook/it-and-enablement#test-fleetdm-com-locally).
Please see 📖[handbook/engineering#test-fleetdm-com-locally](https://fleetdm.com/handbook/engineering#test-fleetdm-com-locally).
##### Cloudflare
Please see 📖[handbook/engineering#edit-a-dns-record](https://fleetdm.com/handbook/engineering#edit-a-dns-record).

4
handbook/company/go-to-market-groups.md
View file

@ -9,7 +9,7 @@ When communicating with future or current customers, hand-offs [between departme
> Use this "🦄 Go-To-Market groups" page to write down philosophies and show how the different pieces of the GTM process fit together.
> Use the dedicated departmental handbook pages for [🫧 Marketing](https://fleetdm.com/handbook/marketing), 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement), [🐋 Sales](https://fleetdm.com/handbook/sales), [🌦️ Customer Success](https://fleetdm.com/handbook/customer-success), and [💸 Finance](https://fleetdm.com/handbook/finance) to keep track of specific responsibilities and recurring rituals designed to be read and used within those departments.
> Use the dedicated departmental handbook pages for [🫧 Marketing](https://fleetdm.com/handbook/marketing), 🌐 [IT](https://fleetdm.com/handbook/it), [🐋 Sales](https://fleetdm.com/handbook/sales), [🌦️ Customer Success](https://fleetdm.com/handbook/customer-success), and [💸 Finance](https://fleetdm.com/handbook/finance) to keep track of specific responsibilities and recurring rituals designed to be read and used within those departments.
## Current GTM groups
@ -260,7 +260,7 @@ Use the following steps to send Fleet's vendor collateral to a prospect or custo
### Vendor questionnaires
Occasionally, prospective customers will ask us to complete a questionnaire. In responding to security questionnaires, Fleet endeavors to provide full transparency via our [security policies](https://fleetdm.com/handbook/finance/security#security-policies), [trust](https://trust.fleetdm.com/), and [application security](https://fleetdm.com/handbook/finance/security#application-security) documentation. In addition to this documentation, please refer to [the vendor questionnaires page](https://fleetdm.com/handbook/finance/security#vendor-questionnaires). [Contact the Sales department](https://fleetdm.com/handbook/sales#contact-us) to address any pending questionnaires.
Occasionally, prospective customers will ask us to complete a questionnaire. In responding to security questionnaires, Fleet endeavors to provide full transparency via our [security policies](https://fleetdm.com/handbook/it/security#security-policies), [trust](https://trust.fleetdm.com/), and [application security](https://fleetdm.com/handbook/it/security#application-security) documentation. In addition to this documentation, please refer to [the vendor questionnaires page](https://fleetdm.com/handbook/it/security#vendor-questionnaires). [Contact the Sales department](https://fleetdm.com/handbook/sales#contact-us) to address any pending questionnaires.

6
handbook/company/leadership.md
View file

@ -76,7 +76,7 @@ We structure handbook pages based on audience.
- "This handbook page details processes specific to working `[with](#contact-us)` and `[within](#responsibilities)` this department."
- `## Team`
- Table that displays each position and the team member(s) that fill that position, linking each Fleetie's LinkedIn to their name and GitHub to GitHub user name. See [handbook/it-and-enablement#team](https://fleetdm.com/handbook/it-and-enablement#team) for example.
- Table that displays each position and the team member(s) that fill that position, linking each Fleetie's LinkedIn to their name and GitHub to GitHub user name. See [handbook/people#team](https://fleetdm.com/handbook/people#team) for example.
- `## Contact us`
- "To make a request of this department, `[create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%23{DEPARTMENTAL-GITHUB-LABEL}&projects=&template=1-custom-request.md&title=Request%3A+_______________________)` and a team member will get back to you within one business day (If urgent, mention a `[team member](#team)` in `[:help-DEPARTMENTAL-SLACK-CHANNEL]({DEPARTMENTAL-SLACK-CHANNEL-LINK})`.)"
@ -132,7 +132,7 @@ The board meeting and OKR planning happen during the first week of the third mon
**Day 4 _Plan and finalize_ (virtual):**
- OKR planning (entire E-Group, over Zoom, everyone comes prepared) for 3.5 hours.
- OKR finalization (CEO, EA, Head of People and Head of Digital Workplace & GTM Systems to clean up any details and messaging out to remind/help executives to book time with their teams if it is not booked already for Friday) for 1 hour.
- OKR finalization (CEO, EA, Head of People, and GTM Systems Architect to clean up any details and messaging out to remind/help executives to book time with their teams if it is not booked already for Friday) for 1 hour.
**Day 5 _Communicate_ (virtual):**
- Each manager will work with their team to ratify, understand, and raise any objections or initial edits to the OKRs, all the way down to the ICs.
@ -146,7 +146,7 @@ Every release cycle, each department leader discusses their [key performance ind
In this meeting, the department leader discusses actual week-over-week progress toward the goals for a particular quarter with the CEO.
- Key reviews are scheduled during the e-group time slot every three weeks and are not moved or rescheduled. If a department leader is not available to lead a particular key review, another team member from their department will join the meeting and discuss their department's key performance indicators (KPIs).
- Use this meeting to add, remove, or change the definitions or ownership of KPIs. Otherwise, KPI definitions do not change, even if those definitions have problems. For help with KPIs, contact 🌐 [IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us).
- Use this meeting to add, remove, or change the definitions or ownership of KPIs. Otherwise, KPI definitions do not change, even if those definitions have problems. For help with KPIs, contact [People](https://fleetdm.com/handbook/people#contact-us).
## Hiring

2
handbook/company/writing.md
View file

@ -113,7 +113,7 @@ Our handbook and docs pages are written in Markdown and are editable from our we
When merging a PR to the main branch of the [Fleet repo](https://github.com/fleetdm/fleet), remember that whatever you merge gets deployed live immediately. Ensure that the appropriate quality checks have been completed before merging. [Learn about the website QA process](#quality).
When merging changes to the [docs](https://fleetdm.com/docs), [handbook](https://fleetdm.com/handbook), and articles, make sure that the PR’s changes do not contain inappropriate content (goes without saying) or confidential information, and that the content represents our [brand](#brand) accordingly. When in doubt reach out to the product manager of the [website group](https://fleetdm.com/handbook/it-and-enablement) in the [#g-it-and-enablement](https://fleetdm.slack.com/archives/C058S8PFSK0) channel on Slack.
When merging changes to the [docs](https://fleetdm.com/docs), [handbook](https://fleetdm.com/handbook), and articles, make sure that the PR’s changes do not contain inappropriate content (goes without saying) or confidential information, and that the content represents our [brand](#brand) accordingly. When in doubt reach out to the product manager of the [website group](https://fleetdm.com/handbook/company/product-groups#website-group) in the [#g-website](https://fleetdm.slack.com/archives/C097P4TAPRR) channel on Slack.
### Editing a merged pull request

2
handbook/engineering/README.md
View file

@ -436,7 +436,7 @@ When this occurs, we will begin receiving the following error message when attem
2. Log in using the credentials stored in 1Password under "Apple developer account".
3. Contact the Head of Digital Workplace & GTM Systems to determine which phone number to use for 2FA.
3. Contact the GTM Systems Architect to determine which phone number to use for 2FA.
4. Complete the 2FA process to log in.

57
handbook/finance/README.md
View file

@ -8,6 +8,7 @@ This handbook page details processes specific to working [with](#contact-us) and
|:------------------------------|:-----------------------------------------------------------------------------------------------------------|
| CFO | [Tina Ong](https://www.linkedin.com/in/ongtina/) _([@rfoo2015](https://github.com/rfoo2015))_
| Deal Desk | [Nathan Holliday](https://www.linkedin.com/in/nathanael-holliday/) _([@hollidayn](https://github.com/hollidayn))_
| GTM Systems Architect | [Sam Pfluger](https://www.linkedin.com/in/sampfluger88/) _([@sampfluger88](https://github.com/sampfluger88))_
## Contact us
@ -16,10 +17,14 @@ This handbook page details processes specific to working [with](#contact-us) and
- Please **use issue comments and GitHub mentions** to communicate follow-ups or answer questions related to your request.
- Any Fleet team member can [view the kanban board](https://github.com/orgs/fleetdm/projects/80) for this department, including pending tasks and the status of new requests.
> To **make a request** of the GTM Ops team, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Agtm-ops&projects=&template=1-custom-request.md&title=) and a team member will get back to you within one business day (If urgent, mention [Sam Pfluger](https://fleetdm.slack.com/team/U05CS07KASK) in the [#g-unicorns](https://fleetdm.slack.com/archives/C08BTMFTUCR) Slack channel).
> - Any Fleet team member can [view the kanban board](https://github.com/orgs/fleetdm/projects/100/views/1) for this department, including pending tasks and the status of new requests.
> - Please **use issue comments and GitHub mentions** to communicate follow-ups or answer questions related to your request.
## Responsibilities
The Finance department is directly responsible for accounts receivable including invoicing, accounts payable including commision calculations, compliance, expense reporting including Brex memos and maintaining accurate spend projections in "🧮The numbers", sales taxes, payroll taxes, corporate income/franchise taxes, and financial operations including bank accounts and cash flow management.
The Finance department is directly responsible for accounts receivable including invoicing, accounts payable including commision calculations, compliance, expense reporting including Brex memos and maintaining accurate spend projections in "🧮The numbers", sales taxes, payroll taxes, corporate income/franchise taxes, financial operations including bank accounts and cash flow management, Zapier flows, as well the internal tooling, automation, and technology behind Fleet's Go-To-Market (GTM) systems.
### Prepare for OCV meeting
@ -477,22 +482,56 @@ When an agreement is routed to the [CFO](https://fleetdm.com/handbook/finance#te
3. Click on a test, then click on "Tasks".
4. Click on "Create task." Then, "Create GitHub issue."
5. This will bring you to a screen where you can select the appropriate DRIs and GitHub labels (multiple, if necessary, but always include the ":help-finance" label). Vanta will autopopulate the issue with a brief description of the test due and what needs to be remediated. You can manually add details if necessary.
6. Follow up with the DRI of each issue daily until it's resolved. As needed, loop in their manager, the [Head of People](https://fleetdm.com/handbook/people#team),Fleet's CTO, or the Head of Digital Workplace & GTM Systems. If the test is within 3 days of being overdue, DM the fleetie and their manager, asking to have the issue prioritized and completed before the due date.
6. Follow up with the DRI of each issue daily until it's resolved. As needed, loop in their manager, the [Head of People](https://fleetdm.com/handbook/people#team),Fleet's CTO, or the Head of IT. If the test is within 3 days of being overdue, DM the fleetie and their manager, asking to have the issue prioritized and completed before the due date.
### Check GitHub terms
Go to [GitHub's terms of services](https://docs.github.com/en/free-pro-team@latest/github/site-policy/github-terms-of-service) and search “inbound=outbound” to find the clause, if still there as is, paste a screenshot into the table in this [document](https://docs.google.com/document/d/101rcp9v3Zdml4YolGRmqYS5ruAKzQvXLOTHLXCavPuE/edit#heading=h.xu6qsi0wrns). If the clause has changed, contact Mike M. and let him know.
### Measure intent signals
Daily, follow the steps in the [🦄⚡️🌐 Go-To-Market strategy doc (confidential)](https://github.com/fleetdm/confidential/blob/main/go-to-market-strategy.md#daily) to measure and process intent signals.
### Manage duplicates in CRM
1. For accounts, navigate to the ["Ω Possible duplicate accounts" report](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000001FA1h2AG/view). For Contacts, navigate to the ["Ω Possible duplicate contacts" report](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000002qAoX2AU/view).
2. Verify that each potential duplicate record is indeed a duplicate of the record it has been paired with.
3. Open and compare the duplicate records to select the most up-to-date record to "Use as principal" (the record all other duplicates will be merged into). Consider the following:
- Is there an open opportunity on any of the records? If so, this is your "principal" account/contact.
- Do any of the accounts not have contacts? If no contacts found on the account and no significant activity, delete the account.
- Do any of these accounts/contacts have activity that the others don't have (e.g. a rep sent an email or logged a call)? Be sure to preserve the maximum amount of historical activity on the principal record.
4. Click "View duplicates", select all relevant records that appear. Click next.
5. Select the best and most up-to-date data to combine into the single principal account/contact.
> Do *NOT* change account owners if you can help it during this process. For "non-sales-ready" accounts default to the Integrations Admin. If the account is owned by an active user, be sure they maintain ownership of the principal account.
6. YOU CAN NOT UNDO THIS NEXT PART! Click next, click merge.
7. Verify that the principal record details match exactly what is on LinkedIn.
### Grant role-specific license to a team member
Certain new team members, especially in go-to-market (GTM) roles, will need paid access to paid tools like Salesforce and LinkedIn Sales Navigator immediately on their first day with the company. Gong licenses that other departments need may [request them from the Heap of People](https://fleetdm.com/handbook/people#contact-us) who will make sure there is no license redundancy in that department.
### Add a seat to Salesforce
Here are the steps we take to grant appropriate Salesforce licenses to a new hire:
- Go to ["My Account"](https://fleetdm.lightning.force.com/lightning/n/standard-OnlineSalesHome).
- View contracts -> pick current contract.
- Add the desired number of licenses.
- Sign DocuSign sent to the email.
- The order will be processed in ~30m.
- Once the basic license has been added, you can create a new user using the new team member's `@fleetdm.com` email and assign a license to it.
- To enable email sync for a user:
- Navigate to the [user’s record](https://fleetdm.lightning.force.com/lightning/setup/ManageUsers/home) and scroll to the bottom of the permission set section.
- Add the “Inbox with Einstein Activity Capture” permission set and save.
- Navigate to the ["Einstein Activity Capture Settings"](https://fleetdm.lightning.force.com/lightning/setup/ActivitySyncEngineSettingsMain/home) and click the "Configurations" tab.
- Select "Edit", under "User and Profile Assignments" move the new user's name from "Available" to "Selected", scroll all the way down and click save.
### Review Fleet's US company benefits
Annually, around mid-year, Fleet will be prompted by Gusto to review company benefits. The goal is to keep changes minimal. Follow these steps:
1. Log in to your [Gusto admin account](https://gusto.com/).
2. Navigate to "Benefits" and select "Renewal survey".
3. Complete the survey questions, aiming for minimal changes.
4. Approximately 2-3 months after survery completion, Gusto will suggest plans based on Fleet's responses. Choose plans with minimal changes.
5. Gusto will offer these plans to employees during open enrollment, with new coverage starting 3-4 weeks afterward.
## Rituals

34
handbook/finance/finance.rituals.yml
View file

@ -174,3 +174,37 @@
autoIssue:
labels: [ ":help-finance" ]
repo: "confidential"
-
task: "Complete GTM KPIs"
startedOn: "2024-08-30"
frequency: "Weekly"
description: "Complete GTM KPIs for this week"
moreInfoUrl:
dri: "sampfluger88"
autoIssue:
labels: [ ":gtm-ops" ]
repo: "fleet"
-
task: "Confirm closed lost is happening within 30 days"
startedOn: "2025-01-25"
frequency: "Weekly"
description: "Check Salesforce for opportunities 30 days or older and escalate to sales manager who will follow up with prospect and return the deal to marketing via resting and changing the owner"
moreInfoUrl: "https://fleetdm.com/handbook/sales#review-salesforce-opportunities"
dri: "Sampfluger88"
autoIssue:
labels: [ ":gtm-ops","#g-unicorns" ]
repo: "confidential"
-
task: "Measure intent signals"
startedOn: "2024-08-09"
frequency: "Daily"
description: "Using the instructions in the [🦄⚡️🌐 Go-To-Market strategy doc](https://github.com/fleetdm/confidential/blob/main/go-to-market-strategy.md#daily), measure intent signals."
moreInfoUrl: "https://fleetdm.com/handbook/marketing#measure-intent-signals"
dri: "Sampfluger88"
-
task: "Manage duplicates in CRM"
startedOn: "2025-08-08"
frequency: "Daily"
description: "Daily, clean up any duplicate accounts."
moreInfoUrl: "https://fleetdm.com/handbook/marketing#manage-duplicates-in-crm"
dri: "Sampfluger88"

67
handbook/it-and-enablement/it-and-enablement.rituals.yml
View file

@ -1,67 +0,0 @@
# https://github.com/fleetdm/fleet/pull/13084
-
task: "Prioritize for next sprint" # Title that will actually show in rituals table
startedOn: "2023-08-09" # Needs to align with frequency e.g. if frequency is every thrid Thursday startedOn === any third thursday
frequency: "Triweekly" # must be supported by https://github.com/fleetdm/fleet/blob/dbbb501358e226fa3fdf48865175efe3334c826c/website/scripts/build-static-content.js
description: "Using your departmental kanban board, prioritize and finalize next sprint's goals for your team by draging the appropriate issues to the top of the 'Planned' column and archive everything in the 'Done' column."
moreInfoUrl: "https://fleetdm.com/handbook/company/why-this-way#why-make-work-visible" #URL used to highlight "description:" test in table
dri: "allenhouchins" # DRI for ritual (assignee if autoIssue) (TODO display GitHub proflie pic instead of name or title)
autoIssue:
labels: [ ":help-solutions-consulting" ]
repo: "confidential"
-
task: "Complete GTM KPIs"
startedOn: "2024-08-30"
frequency: "Weekly"
description: "Complete GTM KPIs for this week"
moreInfoUrl:
dri: "sampfluger88"
autoIssue:
labels: [ ":gtm-ops" ]
repo: "fleet"
-
task: "Confirm closed lost is happening within 30 days"
startedOn: "2025-01-25"
frequency: "Weekly"
description: "Check Salesforce for opportunities 30 days or older and escalate to sales manager who will follow up with prospect and return the deal to marketing via resting and changing the owner"
moreInfoUrl: "https://fleetdm.com/handbook/sales#review-salesforce-opportunities"
dri: "Sampfluger88"
autoIssue:
labels: [ ":gtm-ops","#g-unicorns" ]
repo: "confidential"
-
task: "Measure intent signals"
startedOn: "2024-08-09"
frequency: "Daily"
description: "Using the instructions in the [🦄⚡️🌐 Go-To-Market strategy doc](https://github.com/fleetdm/confidential/blob/main/go-to-market-strategy.md#daily), measure intent signals."
moreInfoUrl: "https://fleetdm.com/handbook/marketing#measure-intent-signals"
dri: "Sampfluger88"
-
task: "Manage duplicates in CRM"
startedOn: "2025-08-08"
frequency: "Daily"
description: "Daily, clean up any duplicate accounts."
moreInfoUrl: "https://fleetdm.com/handbook/marketing#manage-duplicates-in-crm"
dri: "Sampfluger88"
-
task: "Downgrade unused license seats"
startedOn: "2024-03-31"
frequency: "Quarterly"
description: "Downgrade unused or questionable license seats on the first Wednesday of every quarter"
moreInfoUrl: "https://fleetdm.com/handbook/it-and-enablement#downgrade-an-unused-license-seat"
dri: "Sampfluger88"
-
task: "Prepare board deck"
startedOn: "2023-09-25"
frequency: "Quarterly"
description: "Prepare slide deck for the next board meeting"
dri: "sampfluger88"
-
task: "Review active eval instances"
startedOn: "2025-08-25"
frequency: "Monthly"
description: "Review [list of active instances](https://github.com/fleetdm/confidential/tree/main/infrastructure/cloud) to see what can be shutdown and deleted."
dri: "allenhouchins"
autoIssue:
labels: [ ":help-solutions-consulting" ]
repo: "confidential"

92
handbook/it-and-enablement/README.md → handbook/it/README.md
View file

@ -1,4 +1,4 @@
# 🌐 IT and Enablement
# 🌐 IT
This page details processes specific to working [with](#contact-us) and [within](#responsibilities) this department.
@ -7,25 +7,20 @@ This page details processes specific to working [with](#contact-us) and [within]
| Role | Contributor(s)
|:----------------------------------------|:----------------------------------------------------------------------|
| Head of IT & Enablement | [Allen Houchins](https://www.linkedin.com/in/allenhouchins/) _([@allenhouchins](https://github.com/allenhouchins))_
| Head of Digital Workplace & GTM Systems | [Sam Pfluger](https://www.linkedin.com/in/sampfluger88/) _([@sampfluger88](https://github.com/sampfluger88))_
| Manager of Training and Enablement | [Brock Walters](https://www.linkedin.com/in/brock-walters-247a2990/) _([@nonpunctual](https://github.com/nonpunctual))_
| Head of IT & Solutions Consulting | [Allen Houchins](https://www.linkedin.com/in/allenhouchins/) _([@allenhouchins](https://github.com/allenhouchins))_
| Solutions Consultant (SC) | <sup><sub> _See [🦄 Go-To-Market groups](https://fleetdm.com/handbook/company/go-to-market-groups#current-gtm-groups)_
## Contact us
- To **make a request** of this department, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-it-and-enablement&projects=&template=1-custom-request.md&title=) and a team member will get back to you within one business day. (If urgent, mention a [team member](#team) in the [#help-it-and-enablement](https://fleetdm.slack.com/archives/C09861YJUJ2) Slack channel.)
- To **make a request** of this department, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Ahelp-it&projects=&template=1-custom-request.md&title=) and a team member will get back to you within one business day. (If urgent, mention a [team member](#team) in the [#help-it](https://fleetdm.slack.com/archives/C09861YJUJ2) Slack channel.)
- Any Fleet team member can [view the kanban board](https://github.com/orgs/fleetdm/projects/69) for this department, including pending tasks and the status of new requests.
- Please **use issue comments and GitHub mentions** to communicate follow-ups or answer questions related to your request.
> To **make a request** of the GTM Ops team, [create an issue](https://github.com/fleetdm/confidential/issues/new?assignees=&labels=%3Agtm-ops&projects=&template=1-custom-request.md&title=) and a team member will get back to you within one business day (If urgent, mention [Sam Pfluger](https://fleetdm.slack.com/team/U05CS07KASK) in the [#g-unicorns](https://fleetdm.slack.com/archives/C08BTMFTUCR) Slack channel).
> - Any Fleet team member can [view the kanban board](https://github.com/orgs/fleetdm/projects/100/views/1) for this department, including pending tasks and the status of new requests.
> - Please **use issue comments and GitHub mentions** to communicate follow-ups or answer questions related to your request.
## Responsibilities
The IT & Enablement department is directly responsible for solutions consulting, customer training curriculum, prospect enablement, and dogfooding, as well as the framework, schema, equipment, internal tooling, automation, and technology behind Fleet's Go-To-Market (GTM) systems, remote work, the handbook, issue templates, Zapier flows, Docusign templates, key spreadsheets, and project management tools.
The IT department is directly responsible for solutions consulting, dogfooding, internal frameworks and schemas, equipment management, and internal IT support.
### Register a domain for Fleet
@ -33,29 +28,6 @@ The IT & Enablement department is directly responsible for solutions consulting,
Domain name registrations are handled through Namecheap. Access is managed via 1Password.
### Purchase a SaaS tool
When procuring SaaS tools and services, analyze the purchase of these subscription services look for these way to help the company:
- Get product demos whenever possible. Does the product do what it's supposed to do in the way that it is supposed to do it?
- Avoid extra features you don't need, and if they're there anyway, avoid using them.
- Data portability: is it possible for Fleet to export it's data if we stop using it? Is it easy to pull that data in an understandable format?
- Programmability: Does it have a publicly documented legible REST API that requires at most a single API token?
- Intentionality: The product fits into other tools and processes that Fleet uses today. Avoid [unintended consequences](https://en.wikipedia.org/wiki/Midas). The tool will change to fit the company, or we won't use it.
### Cancel a vendor or subscription
Once the decision has been made not to renew a tool or subscription on Fleet's behalf, use the following steps to churn/cancel a vendor or subscription:
1. Cancel the subscription, including recurring billing. If invoiced, then send churn notice.
2. Update ["¶ 🧮 The numbers" spreadsheet (confidential doc)](https://docs.google.com/spreadsheets/d/1X-brkmUK7_Rgp7aq42drNcUg8ZipzEiS153uKZSabWc/edit?gid=2112277278#gid=2112277278).
- Prepend the recurring expense title with "CANCELLED - ".
- Zero-out "Projected monthly burn" and "Projected invoice amount".
3. Remove references from integrated systems and references (i.e. unplug the tool from any other integrations)
4. Remove any shared access from 1Password vaults.
5. Update any reference to the tool or subscription and afterwards communicate the change (e.g. by linking to your merged PR in Slack).
### Secure company-issued equipment for a team member
As soon as an offer is accepted, Fleet provides laptops and YubiKey security keys for core team members to use while working at Fleet. The IT engineer will work with the new team member to get their equipment requested and shipped to them on time.
@ -100,72 +72,20 @@ Once the department approves inventory to be shipped from Fleet IT, follow these
1. Compare the equipment request issue with the ["📦 Warehouse" team](https://dogfood.fleetdm.com/settings/teams/users?team_id=279) and verify physical inventory.
2. Plug in the device and ensure inventory has been correctly processed and all components are present (e.g. charger cord, power converter).
3. Package equipment for shipment and include Yubikeys (if requested).
4. Change the "host" info to reflect the new user. If you encounter any issues, repeat the [process incoming equipment steps](https://fleetdm.com/handbook/it-and-enablement#process-incoming-equipment).
4. Change the "host" info to reflect the new user. If you encounter any issues, repeat the [process incoming equipment steps](https://fleetdm.com/handbook/it#process-incoming-equipment).
6. Ship via FedEx to the address listed in the equipment request.
7. Add a comment to the equipment request issue, at-mentioning the requestor with the FedEx tracking info and close the issue.
### Grant role-specific license to a team member
Certain new team members, especially in go-to-market (GTM) roles, will need paid access to paid tools like Salesforce and LinkedIn Sales Navigator immediately on their first day with the company. Gong licenses that other departments need may [request them from IT & Enablement](https://fleetdm.com/handbook/it-and-enablement#contact-us) and we will make sure there is no license redundancy in that department.
### Process a tool upgrade request from a team member
- A Fleetie may request an upgraded license seat for Fleet tools by submitting an issue through GitHub.
- IT & Enablement will upgrade or add the license seat as needed and let the requesting team member know they did it.
### Downgrade an unused license seat
- On the first Wednesday of every quarter, the CEO and Head of Digital Workplace & GTM Systems will meet for 30 minutes to audit license seats in Figma, Slack, GitHub, Salesforce and other tools.
- During this meeting, as many seats will be downgraded as possible. When doubt exists, downgrade.
- Afterward, post in #random letting folks know that the quarterly tool reconciliation and seat clearing is complete, and that any members who lost access to anything they still need can submit a GitHub issue to IT & Enablement to have their access restored.
- The goal is to build deep, integrated knowledge of tool usage across Fleet and cut costs whenever possible. It will also force conversations on redundancies and decisions that aren't helping the business that otherwise might not be looked at a second time.
### Add a seat to Salesforce
Here are the steps we take to grant appropriate Salesforce licenses to a new hire:
- Go to ["My Account"](https://fleetdm.lightning.force.com/lightning/n/standard-OnlineSalesHome).
- View contracts -> pick current contract.
- Add the desired number of licenses.
- Sign DocuSign sent to the email.
- The order will be processed in ~30m.
- Once the basic license has been added, you can create a new user using the new team member's `@fleetdm.com` email and assign a license to it.
- To enable email sync for a user:
- Navigate to the [user’s record](https://fleetdm.lightning.force.com/lightning/setup/ManageUsers/home) and scroll to the bottom of the permission set section.
- Add the “Inbox with Einstein Activity Capture” permission set and save.
- Navigate to the ["Einstein Activity Capture Settings"](https://fleetdm.lightning.force.com/lightning/setup/ActivitySyncEngineSettingsMain/home) and click the "Configurations" tab.
- Select "Edit", under "User and Profile Assignments" move the new user's name from "Available" to "Selected", scroll all the way down and click save.
### Measure intent signals
Daily, follow the steps in the [🦄⚡️🌐 Go-To-Market strategy doc (confidential)](https://github.com/fleetdm/confidential/blob/main/go-to-market-strategy.md#daily) to measure and process intent signals.
### Manage duplicates in CRM
1. For accounts, navigate to the ["Ω Possible duplicate accounts" report](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000001FA1h2AG/view). For Contacts, navigate to the ["Ω Possible duplicate contacts" report](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000002qAoX2AU/view).
2. Verify that each potential duplicate record is indeed a duplicate of the record it has been paired with.
3. Open and compare the duplicate records to select the most up-to-date record to "Use as principal" (the record all other duplicates will be merged into). Consider the following:
- Is there an open opportunity on any of the records? If so, this is your "principal" account/contact.
- Do any of the accounts not have contacts? If no contacts found on the account and no significant activity, delete the account.
- Do any of these accounts/contacts have activity that the others don't have (e.g. a rep sent an email or logged a call)? Be sure to preserve the maximum amount of historical activity on the principal record.
4. Click "View duplicates", select all relevant records that appear. Click next.
5. Select the best and most up-to-date data to combine into the single principal account/contact.
> Do *NOT* change account owners if you can help it during this process. For "non-sales-ready" accounts default to the Integrations Admin. If the account is owned by an active user, be sure they maintain ownership of the principal account.
6. YOU CAN NOT UNDO THIS NEXT PART! Click next, click merge.
7. Verify that the principal record details match exactly what is on LinkedIn.
## Rituals
<rituals :rituals="rituals['handbook/it-and-enablement/it-and-enablement.rituals.yml']"></rituals>
<rituals :rituals="rituals['handbook/it/it.rituals.yml']"></rituals>
#### Stubs

20
handbook/it/it.rituals.yml Normal file
View file

@ -0,0 +1,20 @@
# https://github.com/fleetdm/fleet/pull/13084
-
task: "Prioritize for next sprint" # Title that will actually show in rituals table
startedOn: "2023-08-09" # Needs to align with frequency e.g. if frequency is every thrid Thursday startedOn === any third thursday
frequency: "Triweekly" # must be supported by https://github.com/fleetdm/fleet/blob/dbbb501358e226fa3fdf48865175efe3334c826c/website/scripts/build-static-content.js
description: "Using your departmental kanban board, prioritize and finalize next sprint's goals for your team by draging the appropriate issues to the top of the 'Planned' column and archive everything in the 'Done' column."
moreInfoUrl: "https://fleetdm.com/handbook/company/why-this-way#why-make-work-visible" #URL used to highlight "description:" test in table
dri: "allenhouchins" # DRI for ritual (assignee if autoIssue) (TODO display GitHub proflie pic instead of name or title)
autoIssue:
labels: [ ":help-solutions-consulting" ]
repo: "confidential"
-
task: "Review active eval instances"
startedOn: "2025-08-25"
frequency: "Monthly"
description: "Review [list of active instances](https://github.com/fleetdm/confidential/tree/main/infrastructure/cloud) to see what can be shutdown and deleted."
dri: "allenhouchins"
autoIssue:
labels: [ ":help-solutions-consulting" ]
repo: "confidential"

50
handbook/finance/security.md → handbook/it/security.md
View file

@ -11,17 +11,17 @@ As an all-remote company, we do not have the luxury of seeing each other or bein
| Participant | Role |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Requester | Requests recovery for their own account |
| Recoverer | Person with access to perform the recovery who monitors `help-it-and-enablement` |
| Recoverer | Person with access to perform the recovery who monitors `help-it` |
| Identifier | Person that visually identifies the requester in a video call. The identifier can be the recoverer or a person the recoverer can recognize visually |
### Preparing for recovery
1. If the requester still has access to GitHub and/or Slack, they [ask for
help](https://fleetdm.com/handbook/it-and-enablement#contact-us). For non-urgent requests, please
help](https://fleetdm.com/handbook/it#contact-us). For non-urgent requests, please
prefer filing an issue with the IT & Enablement team. If they do not have access,
they can contact their manager or a teammate over the phone via voice or texting, and they will
[ask for help](https://fleetdm.com/handbook/it-and-enablement#contact-us) on behalf of the
[ask for help](https://fleetdm.com/handbook/it#contact-us) on behalf of the
requester.
2. The recoverer identifies the requester through a live video call.
* If the recoverer does not know the requester well enough to positively identify them visually, the
@ -344,7 +344,7 @@ is kept up to date.
We strongly recommend using hardware security keys. Fleet configures privileged user accounts with a policy that enforces the use of hardware security keys. This prevents credential theft better than other methods of 2FA/2-SV. If you do not already have a pair of hardware security keys, order [two YubiKey 5C NFC security
keys](https://www.yubico.com/us/product/yubikey-5-nfc/) with your company card, or ask
for help in [#help-it-and-enablement](https://fleetdm.slack.com/archives/C09861YJUJ2) to get one if you do not have a company card.
for help in [#help-it](https://fleetdm.slack.com/archives/C09861YJUJ2) to get one if you do not have a company card.
#### Are they YubiKeys or security keys?
@ -362,7 +362,7 @@ Because they are the only type of Two-Factor Authentication (2FA) that protects
phishing, we will make them **mandatory for everyone** soon.
See the [Google Workspace security
section](https://fleetdm.com/handbook/finance/security#2-step-verification) for more
section](https://fleetdm.com/handbook/it/security#2-step-verification) for more
information on the security of different types of 2FA.
@ -649,7 +649,7 @@ We apply the following *Security/Password management* settings to all users as t
| Allow password reuse | Disabled |
| Expiration | Never expires |
We also configure [Password Alert](https://support.google.com/chrome/a/answer/9696707?visit_id=637806265550953415-394435698&rd=1#zippy=) to warn users of password re-use. See [How we protect end-user devices](https://fleetdm.com/handbook/finance/security#how-we-protect-end-user-devices).
We also configure [Password Alert](https://support.google.com/chrome/a/answer/9696707?visit_id=637806265550953415-394435698&rd=1#zippy=) to warn users of password re-use. See [How we protect end-user devices](https://fleetdm.com/handbook/it/security#how-we-protect-end-user-devices).
#### Account recovery
@ -942,9 +942,9 @@ Fleet requires all team members to comply with the following acceptable use requ
- Anti-malware or equivalent protection and monitoring must be installed and enabled on all endpoint systems that may be affected by malware, including workstations, laptops, and servers. This is automatically enforced on Fleet-managed macOS devices and must be manually configured for any unmanaged workstations.
- Teams must exclusively use legal software with a valid license installed through the "app store" or trusted sources. Well-documented open source software can be used. If in doubt, ask in [#help-it-and-enablement](https://fleetdm.slack.com/archives/C09861YJUJ2).
- Teams must exclusively use legal software with a valid license installed through the "app store" or trusted sources. Well-documented open source software can be used. If in doubt, ask in [#help-it](https://fleetdm.slack.com/archives/C09861YJUJ2).
- Avoid sharing credentials. Secrets must be stored safely, using features such as GitHub secrets. For accounts and other sensitive data that need to be shared, use the company-provided password manager (1Password). If you don't know how to use the password manager or safely access secrets, please ask in [#help-it-and-enablement](https://fleetdm.slack.com/archives/C09861YJUJ2)!
- Avoid sharing credentials. Secrets must be stored safely, using features such as GitHub secrets. For accounts and other sensitive data that need to be shared, use the company-provided password manager (1Password). If you don't know how to use the password manager or safely access secrets, please ask in [#help-it](https://fleetdm.slack.com/archives/C09861YJUJ2)!
- Sanitize and remove any sensitive or confidential information prior to posting. At Fleet, we are public by default. Sensitive information from logs, screenshots, or other types of data (eg. debug profiles) should not be shared publicly.
@ -989,17 +989,17 @@ Fleet requires all workforce members to comply with the following acceptable use
- [Asset management policy](https://fleetdm.com/handbook/finance/security#asset-management-policy)
- [Business continuity and disaster recovery policy](https://fleetdm.com/handbook/finance/security#business-continuity-and-disaster-recovery-policy)
- [Data management policy](https://fleetdm.com/handbook/finance/security#data-management-policy)
- [Encryption policy](https://fleetdm.com/handbook/finance/security#encryption-policy)
- [Human resources security policy](https://fleetdm.com/handbook/finance/security#human-resources-security-policy)
- [Incident response policy](https://fleetdm.com/handbook/finance/security#incident-response-policy)
- [Operations security and change management policy](https://fleetdm.com/handbook/finance/security#operations-security-and-change-management-policy)
- [Risk management policy](https://fleetdm.com/handbook/finance/security#risk-management-policy)
- [Secure software development and product security policy](https://fleetdm.com/handbook/finance/security#secure-software-development-and-product-security-policy)
- [Security policy management policy](https://fleetdm.com/handbook/finance/security#security-policy-management-policy)
- [Third-party management policy](https://fleetdm.com/handbook/finance/security#third-party-management-policy)
- [Asset management policy](https://fleetdm.com/handbook/it/security#asset-management-policy)
- [Business continuity and disaster recovery policy](https://fleetdm.com/handbook/it/security#business-continuity-and-disaster-recovery-policy)
- [Data management policy](https://fleetdm.com/handbook/it/security#data-management-policy)
- [Encryption policy](https://fleetdm.com/handbook/it/security#encryption-policy)
- [Human resources security policy](https://fleetdm.com/handbook/it/security#human-resources-security-policy)
- [Incident response policy](https://fleetdm.com/handbook/it/security#incident-response-policy)
- [Operations security and change management policy](https://fleetdm.com/handbook/it/security#operations-security-and-change-management-policy)
- [Risk management policy](https://fleetdm.com/handbook/it/security#risk-management-policy)
- [Secure software development and product security policy](https://fleetdm.com/handbook/it/security#secure-software-development-and-product-security-policy)
- [Security policy management policy](https://fleetdm.com/handbook/it/security#security-policy-management-policy)
- [Third-party management policy](https://fleetdm.com/handbook/it/security#third-party-management-policy)
### Access authorization and termination
@ -1079,7 +1079,7 @@ For new employees who have not received a company laptop or in cases where a com
| Question | Answer |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Please provide your application/solution disaster recovery RTO/RPO | RTO and RPO intervals differ depending on the service that is impacted. Please refer to https://fleetdm.com/handbook/finance/security-policies#business-continuity-and-disaster-recovery-policy
| Please provide your application/solution disaster recovery RTO/RPO | RTO and RPO intervals differ depending on the service that is impacted. Please refer to https://fleetdm.com/handbook/it/security-policies#business-continuity-and-disaster-recovery-policy
> _Created from [JupiterOne/security-policy-templates](https://github.com/JupiterOne/security-policy-templates). [CC BY-SA 4 license](https://creativecommons.org/licenses/by-sa/4.0/)_
@ -1113,7 +1113,7 @@ For technical incidents:
For business/operational incidents:
- CEO (Mike McNeil)
- Head of Digital Workplace & GTM Systems (Sam Pfluger)
- GTM Systems Architect (Sam Pfluger)
### Response Teams and Responsibilities
@ -1887,7 +1887,7 @@ so within a week of a report.
Libraries are inventoried and monitored for vulnerabilities. Our process for fixing vulnerable
libraries and other vulnerabilities is available in our
[handbook](https://fleetdm.com/handbook/finance/security#vulnerability-management). We use
[handbook](https://fleetdm.com/handbook/it/security#vulnerability-management). We use
[Dependabot](https://github.com/dependabot) to automatically open PRs to update vulnerable dependencies.
@ -2017,7 +2017,7 @@ This was resolved on 2025-07-30 in the `fleetdm/fleet-terraform` with [updates T
The web application did not enforce user lockouts as a result of brute-force password attacks. The tester sent 20 fake passwords to the application in 5-second delays to avoid the rate limiting in place by the application.
This was previously documented and addressed as [a finding in our 2022 penetration test](https://fleetdm.com/handbook/finance/security#5-no-account-lockout).
This was previously documented and addressed as [a finding in our 2022 penetration test](https://fleetdm.com/handbook/it/security#5-no-account-lockout).
#### 3 - Long session timeout
@ -2027,7 +2027,7 @@ This was previously documented and addressed as [a finding in our 2022 penetrati
The default value was found to be five days, but session timeout is configurable for self-managed users in the application's configuration.
This was previously documented and addressed as [a finding in our 2022 penetration test](https://fleetdm.com/handbook/finance/security#6-session-timeout-insufficient-session-expiration).
This was previously documented and addressed as [a finding in our 2022 penetration test](https://fleetdm.com/handbook/it/security#6-session-timeout-insufficient-session-expiration).
#### 4 - Failure to validate new account emails
@ -2047,7 +2047,7 @@ All user accounts that use email and password for authentication require an admi
The application's authentication token was stored in the browser's DOM storage object.
This was previously documented and addressed as [a finding in our 2022 penetration test](https://fleetdm.com/handbook/finance/security#4-insecure-storage-of-authentication-tokens).
This was previously documented and addressed as [a finding in our 2022 penetration test](https://fleetdm.com/handbook/it/security#4-insecure-storage-of-authentication-tokens).
### June 2024 penetration testing of Fleet 4.50.1

3
handbook/marketing/README.md
View file

@ -10,6 +10,7 @@ This handbook page details processes specific to working [with](#contact-us) and
| Chief Marketing Officer | [Ashish Kuthiala](https://www.linkedin.com/in/ashishkuthiala) _([@akuthiala](https://github.com/akuthiala))_
| Content Specialist | [Irena Reedy](https://www.linkedin.com/in/irena-reedy-520ab9354/) _([@irenareedy](https://github.com/irenareedy))_
| Head of Demand Generation | [John Jeremiah](https://www.linkedin.com/in/johnjeremiah/) _([@johnjeremiah](https://github.com/johnjeremiah))_
| Product Education Manager | [Brock Walters](https://www.linkedin.com/in/brock-walters-247a2990/) _([@nonpunctual](https://github.com/nonpunctual))_
## Contact us
@ -20,7 +21,7 @@ This handbook page details processes specific to working [with](#contact-us) and
## Responsibilities
The Marketing department is directly responsible for achieving revenue pipeline targets, increasing awareness and interest in the open-source project, and nurturing the Fleet community through participation in video, sponsored events, and other [programs](https://fleetdm.com/handbook/company/communications#programs).
The Marketing department is directly responsible for achieving revenue pipeline targets, increasing awareness and interest in the open-source project, customer training curriculums, prospect enablement, and nurturing the Fleet community through participation in video, sponsored events, and other [programs](https://fleetdm.com/handbook/company/communications#programs).
### Organize work in GitHub issues with marketing labels

39
handbook/people/README.md
View file

@ -20,7 +20,7 @@ This page details processes specific to working [with](#contact-us) and [within]
## Responsibilities
The People department is directly responsible for Fleet's culture, human resources, benefits, opening positions, compensation planning, onboarding, and offboarding. For Executive Assistant responsibilities, see the [🔭 CEO](https://fleetdm.com/handbook/ceo#responsibilities) page.
The People department is directly responsible for Fleet's culture, human resources, benefits, opening positions, compensation planning, onboarding, offboarding, remote work, the handbook, issue templates, Docusign templates, key spreadsheets, and project management tools. For Executive Assistant responsibilities, see the [🔭 CEO](https://fleetdm.com/handbook/ceo#responsibilities) page.
> Commission planning, taxes, state unemployment insurance filings, business insurance, Delaware registered agent and franchise taxes, virtual mailbox, company phone number, and other adjacent areas of responsibility are run by [the Finance department](https://fleetdm.com/handbook/finance).
@ -309,6 +309,43 @@ Annually, around mid-year, Fleet will be prompted by Gusto to review company ben
5. Gusto will offer these plans to employees during open enrollment, with new coverage starting 3-4 weeks afterward.
### Purchase a SaaS tool
When procuring SaaS tools and services, analyze the purchase of these subscription services look for these way to help the company:
- Get product demos whenever possible. Does the product do what it's supposed to do in the way that it is supposed to do it?
- Avoid extra features you don't need, and if they're there anyway, avoid using them.
- Data portability: is it possible for Fleet to export it's data if we stop using it? Is it easy to pull that data in an understandable format?
- Programmability: Does it have a publicly documented legible REST API that requires at most a single API token?
- Intentionality: The product fits into other tools and processes that Fleet uses today. Avoid [unintended consequences](https://en.wikipedia.org/wiki/Midas). The tool will change to fit the company, or we won't use it.
### Downgrade an unused license seat
- On the first Wednesday of every quarter, the Head of People will audit license seats in Figma, Slack, GitHub, Salesforce and other tools.
- During this time, as many seats will be downgraded as possible. When doubt exists, downgrade.
- Afterward, post in #random letting folks know that the quarterly tool reconciliation and seat clearing is complete, and that any members who lost access to anything they still need can submit a GitHub issue to the People department to have their access restored.
- The goal is to build deep, integrated knowledge of tool usage across Fleet and cut costs whenever possible. It will also force conversations on redundancies and decisions that aren't helping the business that otherwise might not be looked at a second time.
### Process a tool upgrade request from a team member
- A Fleetie may request an upgraded license seat for Fleet tools by submitting an issue through GitHub.
- The Head of People will upgrade or add the license seat as needed and let the requesting team member know they did it.
### Cancel a vendor or subscription
Once the decision has been made not to renew a tool or subscription on Fleet's behalf, use the following steps to churn/cancel a vendor or subscription:
1. Cancel the subscription, including recurring billing. If invoiced, then send churn notice.
2. Update ["¶ 🧮 The numbers" spreadsheet (confidential doc)](https://docs.google.com/spreadsheets/d/1X-brkmUK7_Rgp7aq42drNcUg8ZipzEiS153uKZSabWc/edit?gid=2112277278#gid=2112277278).
- Prepend the recurring expense title with "CANCELLED - ".
- Zero-out "Projected monthly burn" and "Projected invoice amount".
3. Remove references from integrated systems and references (i.e. unplug the tool from any other integrations)
4. Remove any shared access from 1Password vaults.
5. Update any reference to the tool or subscription and afterwards communicate the change (e.g. by linking to your merged PR in Slack).
## Rituals
<rituals :rituals="rituals['handbook/people/people.rituals.yml']"></rituals>

48
handbook/people/people.rituals.yml
View file

@ -1,47 +1,53 @@
-
task: "Recognize and benchmark workiversaries"
- task: "Recognize and benchmark workiversaries"
startedOn: "2024-07-15"
frequency: "Monthly"
description: "Identify workiversaries coming up in the next two months and follow the steps to ensure they're recognized and benchmarked"
description: "Identify workiversaries coming up in the next two months and follow the steps to ensure they're recognized and benchmarked."
moreInfoUrl: "https://fleetdm.com/handbook/people#recognize-employee-workiversaries"
dri: "ireedy"
autoIssue:
labels: [ ":help-people" ]
labels: [":help-people"]
repo: "confidential"
-
task: "Prepare all hands deck"
- task: "Prepare all hands deck"
startedOn: "2023-07-01"
frequency: "Monthly"
description: "Preparing the all hands deck"
description: "Preparing the all-hands deck."
moreInfoUrl: "https://fleetdm.com/handbook/people#preparing-for-the-all-hands"
dri: "ireedy"
autoIssue:
labels: [ ":help-people" ]
labels: [":help-people"]
repo: "confidential"
-
task: "Share recording of all hands meeting"
- task: "Share recording of all hands meeting"
startedOn: "2023-07-01"
frequency: "Monthly"
description: "Sharing the all hands recording"
description: "Share the all-hands recording."
moreInfoUrl: "https://fleetdm.com/handbook/people#share-recording-of-all-hands-meeting"
dri: "ireedy"
-
task: "Run regular payroll"
- task: "Downgrade unused license seats"
startedOn: "2024-03-31"
frequency: "Quarterly"
description: "Downgrade unused or questionable license seats on the first Wednesday of every quarter."
moreInfoUrl: "https://fleetdm.com/handbook/people#downgrade-an-unused-license-seat"
dri: "ireedy"
- task: "Prepare board deck"
startedOn: "2023-09-25"
frequency: "Quarterly"
description: "Prepare slide deck for the next board meeting."
dri: "ireedy"
- task: "Run regular payroll"
startedOn: "2024-02-24"
frequency: "Monthly"
description: "Verify auto-populated payroll for all full time employees is accurate, and approve for processing."
moreInfoUrl: "https://fleetdm.com/handbook/finance#run-payroll"
description: "Verify auto-populated payroll for all full-time employees is accurate, and approve for processing."
moreInfoUrl: "https://fleetdm.com/handbook/poeple#run-payroll"
dri: "ireedy"
autoIssue:
labels: [ ":help-people" ]
labels: [":help-people"]
repo: "confidential"
-
task: "Run US contractor payroll"
- task: "Run US contractor payroll"
startedOn: "2024-02-27"
frequency: "Monthly"
description: "Manually process US contractor payroll by verifying and syncing time contractor worked, then processing payment."
moreInfoUrl: "https://fleetdm.com/handbook/finance#run-us-contractor-payroll"
description: "Manually process US contractor payroll by verifying and syncing the time the contractor worked, then processing the payment."
moreInfoUrl: "https://fleetdm.com/handbook/people#run-us-contractor-payroll"
dri: "ireedy"
autoIssue:
labels: [ ":help-people" ]
labels: [":help-people"]
repo: "confidential"

8
handbook/sales/README.md
View file

@ -30,7 +30,7 @@ The Sales department is directly responsible for attaining the revenue goals of
Use the following steps to add an account to Salesforce if one doesn't exist already:
1. Obtain the company name, website, and LinkedIn company url of the account you would like to create and search Salesforce to be sure a duplicate, parent, or child account doesn't already exist.
2. If the account already exists, reach out to the [Head of Digital Workspace & GTM Systems](https://fleetdm.com/handbook/it-and-enablement#team) in the [#g-unicorns Slack channel](https://fleetdm.slack.com/archives/C08BTMFTUCR) with the account data and request the account be created and/or added to your patch.
2. If the account already exists, reach out to the [GTM Systems Architect](https://fleetdm.com/handbook/finance#team) in the [#g-unicorns Slack channel](https://fleetdm.slack.com/archives/C08BTMFTUCR) with the account data and request the account be created and/or added to your patch.
### Respond to a customer feature comparison request
@ -67,7 +67,7 @@ Use the following steps to change a contact's organization in Salesforce:
### Review Salesforce opportunities
Every week, the sales manager will review the necessary opportunities with internal stakeholders. The AE or CSM who owned the deal, their manager, the Head of Marketing, Head of Digital Workplace & GTM Systems, and the CEO will review all opportunities on the "[Ω Ops for review](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000001qyE12AI/view?queryScope=userFolders)" report in Salesforce. Opportunities will be reviewed for a number of reasons, including:
Every week, the sales manager will review the necessary opportunities with internal stakeholders. The AE or CSM who owned the deal, their manager, the Head of Marketing, GTM Systems Architect, and the CEO will review all opportunities on the "[Ω Ops for review](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG000001qyE12AI/view?queryScope=userFolders)" report in Salesforce. Opportunities will be reviewed for a number of reasons, including:
- If the opportunity is older than 30 days, but the prospect hasn't been sent an order form yet.
- Any closed-lost new business or expansion opportunity from the previous week.
- Any opportunity with a closed date pushed into a different quarter.
@ -78,7 +78,7 @@ If no opportunities meet these criteria, the meeting is used to discuss the olde
### Communicate Gross new ARR added
Once a week, during the "🤝❌ Closed (for now) opportunity review" meeting, the CEO and CRO will measure the amount of "Gross new ARR" added towards the goal set forth by the CEO. To do this:
1. Before the meeting, the [Head of Digital Workplace & GTM Systems](https://fleetdm.com/handbook/it-and-enablement#team) will copy the goal from the gross new ARR goal from ["OCV GOH: Fleet" doc (confidential document)](https://docs.google.com/document/d/17VK0_pRrFGTqKCRfppIjUgfjdL012Ssirks8Jxk4SE4/edit?tab=t.0) and add it to the [🤝❌ Closed (for now) opportunity review (confidential doc)](https://docs.google.com/document/d/12cXSZAervdpAuOImN0Lx0B9n-uYND_tzmPbFr4gMwkU/edit?tab=t.0).
1. Before the meeting, the [GTM Systems Architect](https://fleetdm.com/handbook/finance#team) will copy the goal from the gross new ARR goal from ["OCV GOH: Fleet" doc (confidential document)](https://docs.google.com/document/d/17VK0_pRrFGTqKCRfppIjUgfjdL012Ssirks8Jxk4SE4/edit?tab=t.0) and add it to the [🤝❌ Closed (for now) opportunity review (confidential doc)](https://docs.google.com/document/d/12cXSZAervdpAuOImN0Lx0B9n-uYND_tzmPbFr4gMwkU/edit?tab=t.0).
2. Before the meeting, the Executive Assistant will take a screenshot of the [Ω Open ops (Next 45 days) oppty list](https://fleetdm.lightning.force.com/lightning/o/Opportunity/list?filterName=Open_ops_Next_45_days) that includes the next 5+ deals set to close based on "Close date" and add it to the doc.
3. Using the ["Ω ∆ARR won + open pipeline (current Q)" Salesforce report](https://fleetdm.lightning.force.com/lightning/r/Report/00OUG0000019LuH2AU/view) (and adjusting the filters if needed), the Executive Assistant will calculate the progress toward the goal and "Amount left to close" and add it to the doc.
4. The CRO will paste a screenshot of the progress toward the goal and the actionable next steps from the [🤝❌ Closed (for now) opportunity review (confidential doc)](https://docs.google.com/document/d/12cXSZAervdpAuOImN0Lx0B9n-uYND_tzmPbFr4gMwkU/edit?tab=t.0) in the [#g-unicorns Slack channel](https://fleetdm.slack.com/archives/C08BTMFTUCR).
@ -134,7 +134,7 @@ Account Executives (AEs) are responsible for the project management and completi
To complete a security questionnaire, the AE assigned to the account will:
1. Create an issue linking the questionnaire and any other context needed.
2. [Use the handbook](https://fleetdm.com/handbook/finance/security#vendor-questionnaires) to answer the questions with links to appropriate sections in the handbook.
2. [Use the handbook](https://fleetdm.com/handbook/it/security#vendor-questionnaires) to answer the questions with links to appropriate sections in the handbook.
3. If there are outstanding questions, the AE will assign the issue to the Solutions Consultant (SC) associated with the opportunity.
4. The SC will search for unanswered questions and confirm again that nothing was missed from the handbook. Content missing from the handbook will need to be added via PR by the AE.
5. If there are still unanswered questions, the AE will route the issue to the relevant department. Once complete, the team will leave a comment in the issue, @`mentioning the AE with the requested information. Any questions answered by other departments will be added to the handbook by the AE.

14
it-and-security/lib/macos/configuration-profiles/google-chrome-managed-bookmarks.mobileconfig
View file

@ -64,7 +64,7 @@
<key>name</key>
<string>🔐 Security (Handbook)</string>
<key>url</key>
<string>https://fleetdm.com/handbook/finance/security#security</string>
<string>https://fleetdm.com/handbook/it/security#security</string>
</dict>
<dict>
<key>name</key>
@ -722,20 +722,20 @@
</dict>
<dict>
<key>name</key>
<string>🌐 IT &amp; Enablement</string>
<string>🌐 IT</string>
<key>children</key>
<array>
<dict>
<key>name</key>
<string>🌐 IT &amp; Enablement (Handbook)</string>
<string>🌐 IT (Handbook)</string>
<key>url</key>
<string>https://fleetdm.com/handbook/it-and-enablement</string>
<string>https://fleetdm.com/handbook/it</string>
</dict>
<dict>
<key>name</key>
<string>🌐 Kanban board (:help-it-and-enablement)</string>
<string>🌐 Kanban board (:help-it)</string>
<key>url</key>
<string>https://github.com/orgs/fleetdm/projects/69</string>
<string>https://github.com/orgs/fleetdm/projects/101</string>
</dict>
<dict>
<key>name</key>
@ -753,7 +753,7 @@
<key>name</key>
<string>Account recovery process | Security</string>
<key>url</key>
<string>https://fleetdm.com/handbook/finance/security#account-recovery-process</string>
<string>https://fleetdm.com/handbook/it/security#account-recovery-process</string>
</dict>
<dict>
<key>name</key>

2
it-and-security/lib/macos/configuration-profiles/nudge-configuration.mobileconfig
View file

@ -140,7 +140,7 @@ This window will appear periodically to remind you until your computer is fully
If you fail to update by the deadline, access and functionality may be limited. Please update at your earliest convenience to avoid any downtime or work disruption.
If you have any questions or need any assistance, please reach out via #help-it-and-enablement in Slack.</string>
If you have any questions or need any assistance, please reach out via #help-it in Slack.</string>
<key>mainHeader</key>
<string>Required software update now available</string>
<key>subHeader</key>

2
it-and-security/lib/macos/policies/install-nudge.yml
View file

@ -2,7 +2,7 @@
query: SELECT 1 WHERE EXISTS (SELECT 1 FROM macos_profiles WHERE identifier = "com.fleetdm.nudge.managed") AND EXISTS (SELECT 1 FROM apps WHERE bundle_identifier = "com.github.macadmins.Nudge" and bundle_short_version LIKE "2.%") AND EXISTS (SELECT 1 FROM package_receipts WHERE package_id = "com.fleetdm.Nudge.assets");
critical: true
description: This policy ensures the Nudge is installed and configured.
resolution: "If you are failing this policy, click Refetch. If you are still failing after Refetch completes, drop a note in #help-it-and-enablement."
resolution: "If you are failing this policy, click Refetch. If you are still failing after Refetch completes, drop a note in #help-it."
run_script:
path: ../scripts/install-nudge.sh
install_software:

4
website/config/custom.js vendored
View file

@ -173,7 +173,7 @@ module.exports.custom = {
'handbook/product-design': 'noahtalerman',
'handbook/finance': 'rfoo2015',
'handbook/people': 'ireedy',
'handbook/it-and-enablement': 'allenhouchins',
'handbook/it': 'allenhouchins',
'handbook/sales': 'sampfluger88',
'handbook/customer-success': 'zayhanlon',
'handbook/marketing': 'akuthiala',
@ -290,7 +290,7 @@ module.exports.custom = {
'handbook/company/writing.md': ['mike-j-thomas', 'mikermcneil', 'sampfluger88'],
'handbook/company/go-to-market-groups.md': ['sampfluger88', 'mikermcneil'],
'handbook/company/leadership.md': ['sampfluger88', 'mikermcneil', 'ireedy'],
'handbook/it-and-enablement': ['sampfluger88', 'mikermcneil', 'allenhouchins'],
'handbook/it': ['sampfluger88', 'mikermcneil', 'allenhouchins'],
'handbook/finance': ['sampfluger88', 'mikermcneil', 'rfoo2015'],
'handbook/sales': ['sampfluger88', 'mikermcneil'],
'handbook/marketing': ['sampfluger88', 'mikermcneil', 'akuthiala'],

18
website/config/routes.js vendored
View file

@ -650,13 +650,13 @@ module.exports.routes = {
'GET /device-management/fleet-user-stories-f100': '/success-stories/fleet-user-stories-wayfair',
'GET /device-management/fleet-user-stories-schrodinger': '/success-stories/fleet-user-stories-wayfair',
'GET /device-management/fleet-user-stories-wayfair': '/success-stories/fleet-user-stories-wayfair',
'GET /handbook/security': '/handbook/finance/security',
'GET /handbook/digital-experience/security': '/handbook/finance/security',
'GET /handbook/business-operations/security-policies': '/handbook/finance/security',
'GET /handbook/business-operations/application-security': '/handbook/finance/security',
'GET /handbook/business-operations/security-audits': '/handbook/finance/security',
'GET /handbook/business-operations/security': '/handbook/finance/security',
'GET /handbook/business-operations/vendor-questionnaires': '/handbook/finance/security',
'GET /handbook/security': '/handbook/it/security',
'GET /handbook/digital-experience/security': '/handbook/it/security',
'GET /handbook/business-operations/security-policies': '/handbook/it/security',
'GET /handbook/business-operations/application-security': '/handbook/it/security',
'GET /handbook/business-operations/security-audits': '/handbook/it/security',
'GET /handbook/business-operations/security': '/handbook/it/security',
'GET /handbook/business-operations/vendor-questionnaires': '/handbook/it/security',
'GET /handbook/handbook': '/handbook/company/handbook',
'GET /handbook/company/handbook': '/handbook/company/writing',
'GET /handbook/company/development-groups': '/handbook/company/product-groups',
@ -669,7 +669,7 @@ module.exports.routes = {
'GET /handbook/customers': '/handbook/sales/',
'GET /handbook/product': '/handbook/product-design',
'GET /handbook/business-operations': '/handbook/finance',
'GET /handbook/digital-experience': '/handbook/it-and-enablement',
'GET /handbook/digital-experience': '/handbook/it',
'GET /docs': '/docs/get-started/why-fleet',
'GET /docs/get-started': '/docs/get-started/why-fleet',
@ -687,7 +687,7 @@ module.exports.routes = {
'GET /docs/using-fleet/rest-api': '/docs/rest-api/rest-api',
'GET /docs/using-fleet/configuration-files': '/docs/configuration/configuration-files/',
'GET /docs/using-fleet/application-security': '/handbook/finance/application-security',
'GET /docs/using-fleet/security-audits': '/handbook/finance/security-audits',
'GET /docs/using-fleet/security-audits': '/handbook/it/security-audits',
'GET /docs/using-fleet/process-file-events': '/guides/querying-process-file-events-table-on-centos-7',
'GET /docs/using-fleet/audit-activities': '/docs/using-fleet/audit-logs',
'GET /docs/using-fleet/detail-queries-summary': '/docs/using-fleet/understanding-host-vitals',