Sanka Bot · Actions · Joiners and leavers
Joiner: accounts created
Creates a new joiner's accounts for their first day. Each account, group and license is one action.
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.
- Sanka Bot
- Desk Workflows
- Claude, ChatGPT
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.gitOr a custom connector with the Sanka MCP address.
https://mcp.sanka.com/mcpSign in to Sanka and choose your workspace when Claude asks.
Add Sanka to ChatGPT as a custom MCP server, then sign in.
Add a custom MCP server with the Sanka MCP address and choose OAuth to sign in.
https://mcp.sanka.com/mcpSign in to Sanka and choose your workspace when ChatGPT asks.
Custom MCP servers depend on your ChatGPT plan, and in a company workspace an admin may need to allow them. OpenAI's guide shows where to add one.
Ask in plain words
Try this
Daniel starts on Monday. Please make a Google account and add it to sales@.
Or
- We have two new engineers starting on the 1st.
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.
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.
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.
What happens
- 01Employee
Ask
They write what they need in Slack, Teams or email. They don't have to know which setting it is.
- 02Sanka Bot
Show the change
Sanka Bot works out what changes and shows exactly that before anything runs. Admins and approvers see the price.
- 03Your approver
Approve
Routine requests go straight through. Changes with real impact wait for the right person.
- 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
| App | What happens | Who |
|---|---|---|
| Google Workspace | Creates the account and adds its groups. | Desk does it |
| Google Workspace | Assigns a license. | Your admin does it |
| Okta | Creates the account and adds its groups. | Desk does it |
| Microsoft 365 | Creates the account with its groups and licenses. | Desk, from Microsoft's docs |
| Sanka Flow | Sends the invitation. | Desk does it |
| HubSpot | Adds the user with their role and teams. | Your admin does it |
| Slack | Creates the account and adds its channels. | Your admin does it |
| Salesforce | Creates 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
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.