← All actions

Sanka Bot · Actions · Joiners and leavers

Leaver: accounts suspended

Closes a leaver's access on their last day. Each system is one action.

Desk does itDesk, from Microsoft's docsYour admin does it

See it in action

Ask for it in Claude or ChatGPT. The AI shows what will change and files the ticket only when you say yes. Approvals stay in Sanka.

Starts from
  • Sanka Bot
  • Desk Workflows
  • Claude, ChatGPT
  1. Connect Sanka

    Add Sanka to Claude in either of two ways, then sign in.

    • The Sanka plugin: in the Claude app, open Connectors, choose Add marketplace and paste this address.

      https://github.com/sankaHQ/sanka-plugin.git
    • Or a custom connector with the Sanka MCP address.

      https://mcp.sanka.com/mcp
    • Sign in to Sanka and choose your workspace when Claude asks.

  2. Ask in plain words

    Try this

    Mia's last day is Friday. Please close her access.

    Or

    • Ken left today. Hand his deals to Aiko.
  3. Check the preview and say yes

    The AI shows what changes in each app, who has to approve and the Sanka Credits it uses, then asks “Create this ticket?” Nothing is filed until you say yes.

  4. Approve in Sanka

    When the change needs an approval, the AI gives you the approval link to pass on. The approver opens it and approves in Sanka.

  5. Desk does the work

    Desk makes its changes and reads them back. Steps marked “Your admin does it” go to your admin on the same ticket.

  • An AI client never approves a change.
  • For each integration, your admin chooses who may start its Actions and from where (Sanka Bot, Workflows or AI clients), and can require an approver for every Action an AI client asks for.
  • Desk is switched on per workspace.
  1. You

    Mia's last day is Friday. Please close her access.

  2. Claude

    Here is the preview. Nothing has been filed yet.

    Leaver: accounts suspended

    What changes
    • Sanka FlowMoves their records to the successor and blocks their login.Desk does it
    • Google WorkspaceSuspends the account, signs it out and removes its groups.Desk does it
    • Google WorkspaceDeletes the account and hands its files to the successor.Your admin does it
    • OktaSuspends the account and signs it out.Desk does it
    • Microsoft 365Blocks the account, signs it out and removes its groups and licenses.Desk, from Microsoft's docs
    • SlackDeactivates the account.Your admin does it
    • HubSpotDeactivates the user.Your admin does it
    Approval
    Named here when your rules need one
    Sanka Credits
    100 credits ($1 each)

    Create this ticket?

  3. You

    Yes

  4. Claude

    Filed as ticket #1042. It's waiting for approval. Send this link to your approver.

An example of what the AI shows. The approver, the details and the wording depend on your workspace and its rules.

What happens

  1. 01Employee

    Ask

    They write what they need in Slack, Teams or email. They don't have to know which setting it is.

  2. 02Sanka Bot

    Show the change

    Sanka Bot works out what changes and shows exactly that before anything runs. Admins and approvers see the price.

  3. 03Your approver

    Approve

    Routine requests go straight through. Changes with real impact wait for the right person.

  4. 04Desk

    Apply and read back

    Desk makes the change, reads it back and records it on the ticket. It can roll the change back.

In each app

AppWhat happensWho
Sanka FlowMoves their records to the successor and blocks their login.Desk does it
Google WorkspaceSuspends the account, signs it out and removes its groups.Desk does it
Google WorkspaceDeletes the account and hands its files to the successor.Your admin does it
OktaSuspends the account and signs it out.Desk does it
Microsoft 365Blocks the account, signs it out and removes its groups and licenses.Desk, from Microsoft's docs
SlackDeactivates the account.Your admin does it
HubSpotDeactivates 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.

Hand your L1 requests to Sanka Desk

Start now and ask your first question, or tell us how your employees ask for help today and we'll set Desk up with you.