Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 00:49:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 106

Remove #help-login (#11456)

Browse source 
This reduces the surface area of channels to manage (and the channel is
archived)
This commit is contained in:
Mike McNeil 2023-05-01 12:45:04 -05:00 committed by GitHub
parent 87709d8c95
commit 3b8eaa2323
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 5 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
handbook/business-operations/README.md
View file

@ -875,7 +875,6 @@ These groups maintain the following [Slack channels](https://fleetdm.com/handboo
| Slack channel | [DRI](https://fleetdm.com/handbook/company/why-this-way#why-group-slack-channels) |
|:----------------------------------------|:--------------------------------------------------------------------|
| `#g-business-operations` | Business operations on-call
| `#help-login` | Business operations on-call
| `#help-brex` | Business operations on-call
| `#help-classified` _(¶¶)_ | Business operations on-call
| `#help-onboarding` | Mike McNeil

11
handbook/business-operations/security.md
View file

@ -27,22 +27,21 @@ 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-login* |
| Recoverer | Person with access to perform the recovery who monitors `#g-business-operations` |
| 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 |
Here are the steps we take for the recovery process:
1. If the requester still has access to Slack, they ask for help in `#help-login`. If they do not have access to Slack, they can contact their manager or a teammate over the phone via voice or texting, and they will post in `#help-login` for the requester.
2. A recoverer acknowledges the request in #help-login using the "eyes" emoji 👀.
3. The recoverer identifies the requester through a live video call.
1. If the requester still has access to Slack, they [ask for help](https://fleetdm.com/handbook/business-operations#intake). If they do not have access to Slack, 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/business-operations#intake) 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
recoverer can ask a colleague whom they recognize to act as the identifier. **All three must be
live on a video call at the same time.**
* For example, if the recoverer does not recognize Sam but can recognize Zach, they should ask Zach to identify Sam. Using the requester's manager or a direct teammate is recommended, as it increases the chances they frequently see each other on video.
4. If the recoverer recognizes the requester or has the identity confirmed by the person acting as
the identifier, they can perform the recovery and update the thread in `#help-login`.
3. If the recoverer recognizes the requester or has the identity confirmed by the person acting as
the identifier, they can perform the recovery and update the login recovery issue.
* If the recoverer is not 100% satisfied with identification, they do **NOT** proceed and post to `#help-manage` to engage the security team immediately.