Sanka Desk · Actions · Access, roles and licenses
Perubahan peran atau izin
Mengubah peran atau izin seseorang di satu sistem, misalnya admin, staf, atau hanya lihat.
How employees ask
- Make Kenji an admin in Sanka Flow.
- Mia should only be able to view, not edit.
What happens
- 01Karyawan
Bertanya
They write what they need in Slack, Teams or email. They don't have to know which setting it is.
- 02Sanka Bot
Tampilkan perubahan
Sanka Bot works out what changes and shows exactly that before anything runs. Admins and approvers see the price.
- 03Pemberi persetujuan Anda
Setujui
Permintaan rutin langsung diproses. Perubahan yang berdampak nyata menunggu orang yang tepat.
- 04Desk
Terapkan dan baca ulang
Desk makes the change, reads it back and records it on the ticket. It can roll the change back.
In each app
| Aplikasi | What happens | Who |
|---|---|---|
| Sanka Flow | Sets the role to admin, staff or view-only. | Desk does it |
| Other apps | Changes a role in another app. | 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.
- 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
Serahkan permintaan L1 Anda kepada Sanka Desk
Mulai sekarang dan ajukan pertanyaan pertama Anda, atau beri tahu kami bagaimana karyawan Anda meminta bantuan TI saat ini dan kami akan menyiapkan Desk bersama Anda.