Meeting follow-up
Without Sanka
Decisions become manual tasks that are re-entered after the meeting.
With Sanka
Sakura prepares the corresponding Sanka task, draft, or record from the approved request.
Run governed Sakura workflows from Microsoft Teams.
Ask Sakura from Teams chats and channels, prepare supported Sanka records and workflows, and return approval status and outcomes to the people coordinating the work.
Microsoft Teams workflow automation
Ask anything...
Trusted by 1,000+ teams
%201.png)
Overview
Connect Teams collaboration to accountable operations
Start from the team conversation
Ask Sakura where finance, sales, procurement, HR, or operations are already coordinating the request.
Apply business controls
Sanka checks the requesting user, allowed tools, required fields, and approval path before execution.
Share one final status
Sakura returns completion, exception, and record links so the Teams conversation stays aligned with Sanka.
Tutorial
How Sakura works from Microsoft Teams
- 01Connect Teams and the Sanka workspaceAuthorize the approved Teams connection and map identities to the intended Sanka workspace.
- 02Ask Sakura in chat or a channelDescribe the outcome and let Sakura collect the remaining fields required by the workflow.
- 03Approve and follow the resultReview sensitive actions, then use the returned Sanka link for the final record and audit history.
Compare
Move beyond meeting notes and chat follow-ups
| Workflow | Without Sanka | With Sanka |
|---|---|---|
| Meeting follow-up | Decisions become manual tasks that are re-entered after the meeting. | Sakura prepares the corresponding Sanka task, draft, or record from the approved request. |
| Cross-department work | Sales, finance, procurement, and HR track the same request in different places. | Sanka provides one workflow state and Sakura reports that state back to Teams. |
| Governance | Chat participation does not automatically grant authority to change business records. | Sanka enforces user permissions and approval requirements independently of channel membership. |
Cross-department work
Without Sanka
Sales, finance, procurement, and HR track the same request in different places.
With Sanka
Sanka provides one workflow state and Sakura reports that state back to Teams.
Governance
Without Sanka
Chat participation does not automatically grant authority to change business records.
With Sanka
Sanka enforces user permissions and approval requirements independently of channel membership.
Customer quotes
Don't take our word for it.
Sanka does more than inventory control. It can manage purchasing, billing, orders, and shipping in one place.
As we grew rapidly, we needed a system that could manage purchasing, inbound, inventory sync, and outbound in one place.
At first, we managed everything in Excel. Human error was a constant problem, and our inventory value did not match at fiscal close.
FAQ
Frequently asked questions
Does Teams channel access grant Sanka permissions?
No. Sanka permissions are evaluated separately using the connected identity and workspace policy.
Can Sakura turn meeting decisions into work?
A user can give Sakura the approved decision and request a supported Sanka task, draft, record, or workflow. Sakura should not infer approval solely from meeting attendance.
Where is the authoritative status?
Sakura can report progress in Teams, while the authoritative record, approval state, and execution log remain in Sanka.