Sanka Desk · Actions · 입사·퇴사
퇴사자: 계정 정지
퇴사자의 접근 권한을 마지막 근무일에 막습니다. 시스템마다 작업 1건입니다.
Desk does itDesk, from Microsoft's docsYour admin does it
How employees ask
- Mia's last day is Friday. Please close her access.
- Ken left today. Hand his deals to Aiko.
What happens
- 01직원
질문
They write what they need in Slack, Teams or email. They don't have to know which setting it is.
- 02Sanka Bot
변경 내용 표시
Sanka Bot works out what changes and shows exactly that before anything runs. Admins and approvers see the price.
- 03승인자
승인
일상적인 요청은 바로 처리됩니다. 실제 영향이 있는 변경은 적절한 사람을 기다립니다.
- 04Desk
적용 및 재확인
Desk makes the change, reads it back and records it on the ticket. It can roll the change back.
In each app
| 앱 | What happens | Who |
|---|---|---|
| Sanka Flow | Moves their records to the successor and blocks their login. | Desk does it |
| Google Workspace | Suspends the account, signs it out and removes its groups. | Desk does it |
| Google Workspace | Deletes the account and hands its files to the successor. | Your admin does it |
| Okta | Suspends the account and signs it out. | Desk does it |
| Microsoft 365 | Blocks the account, signs it out and removes its groups and licenses. | Desk, from Microsoft's docs |
| Slack | Deactivates the account. | Your admin does it |
| HubSpot | Deactivates the user. | Your admin does it |
Rows marked “Your admin does it” go to your admin from the same ticket, with the steps written out.
- Desk does it
- Sanka Bot does the work itself. A change through another app's API runs only once that action has passed a write test against the real app, and Desk shows each change first and records it on the ticket.
- Desk, from Microsoft's docs
- Desk follows Microsoft's documentation. These actions have not yet run on a customer's tenant.
- Your admin does it
- Desk takes the request, gets the approval and writes the steps on the ticket. Your own admin does the work and records it there.
Related actions
L1 요청은 Sanka Desk에
지금 바로 시작해 첫 질문을 해 보거나, 현재 직원들이 IT 도움을 어떻게 요청하는지 알려 주십시오. Desk 설정을 함께 진행하겠습니다.