Your team shares what works
Your business AI assistant works in the cloud, and proven procedures can be saved as shared workflows. A colleague can reuse the process in Slack or on the web with their own connected accounts and permissions. Personal preferences stay personal; the team builds on shared methods and results.
It runs in the cloud, not on someone's laptop
Save the method your team can reuse
Keep repeatable marketing, support, and research procedures in Workflows. In My Okou, your Instructions hold your personal preferences; sharing a workflow does not turn those preferences into a shared role.
What one person works out, the whole team builds on
Save a successful procedure as a shared workflow so colleagues can discover and reuse it. Its owner can improve the shared definition; someone who needs their own version can copy it. A private workflow stays personal until it is shared.
Calls competitor-research for each account, then drafts one update per client.
Ask in the channel, and the team sees the answer
Because it runs in the cloud, it is already in Slack. Mention it in a channel to run a shared workflow by name, and the ask, the result, and anyone's amendment stay in one thread the team can read — not in a private chat nobody else can find.
Okourun monthly-client-update for the four active accounts
Done — one update per client, drafted from last month's tickets and calls. View the drafts
Okouadd renewal dates to that workflow so everyone gets them next month
But the access stays personal
Running a shared workflow uses your own connected accounts, approved per connector and per permission, with an expiry. Nobody inherits a teammate's mailbox by running the job they wrote.
Posting this update to Notion needs your approval first.
Notion permissionsAllow insert_contentHow a team reuses a workflow
Share the procedure while each person keeps control of their own connected accounts and permissions.
- 01
Describe a repeatable task
Agree on the inputs, steps, and expected result. Put this job-specific method in a workflow.
- 02
Publish the workflow
Share the workflow with the workspace so a colleague can start from the procedure you have already tested.
- 03
Each member connects their own accounts
Running a shared workflow uses your own services. Nobody inherits a teammate's mailbox or CRM.
- 04
Review what happened
Every run logs the calls it made and the artifacts it produced, so the work is reviewable rather than taken on trust.
What is shared, and what is not
Share workflow instructions and results deliberately. Personal preferences, connected accounts, and permission grants are separate.
Personal preferences
In My Okou, personal Instructions guide your own work. They do not become a shared team profile.
Shared workflow library
The jobs the team has already solved. New members inherit the library on day one.
Personal automations
Triggers belong to whoever set them. Your Monday run is yours, even on a shared workflow.
Per-user credentials
Each member connects their own accounts, so a shared workflow reaches only as far as the person running it.
Permission grants
Approve the connector actions you need, choose a duration, and revoke access when it is no longer needed.
Activity logs
Runs, calls, and outputs are recorded so the work and the identity it ran under can be reviewed.
Everyone connects their own accounts
4,000+ connectors, granted per person — which is what makes a shared workflow safe to hand over.
Axiom
Ahrefs
Airtable
Gmail
Google SheetsNotion
DocuSign
LinearAxiomAhrefsAirtableGmailGoogle SheetsNotionDocuSignLinear
Google Calendar
Intercom
Deel
HubSpot
Dropbox
Sentry
Figma
VercelGoogle CalendarIntercomDeelHubSpotDropboxSentryFigmaVercelThe grant is yours, not the workflow's
A workflow carries instructions, never a credential. It reaches a service only where the person running it has approved that connector.
Scoped and time-boxed
Approve the exact actions a task needs, for the duration you choose. Read stays separate from write.
Revocable in one place
Disconnect your account to remove that saved connection without editing a workflow or affecting a colleague's account.
AI for work: common questions
Does it run on my machine?
No. Runs happen in the cloud, so a scheduled job fires while your laptop is shut and a teammate can run the same workflow from Slack or the web without anything installed.
If I share a workflow, am I sharing my accounts?
No. The workflow is instructions. Whoever runs it uses their own connected services, so a shared job never becomes a shared mailbox.
What can an AI agent for work access?
Yes. Access is approved per connector and per permission rather than as one blanket grant, and it can be time-boxed so it lapses.
What happens when someone leaves?
Shared workflow definitions remain available to the workspace. Other members use their own accounts and permissions; a workflow does not transfer the departing member's connections or personal automations.
Does everyone see everyone else's runs?
Sharing a workflow does not share every chat or run. Visibility depends on what is shared; personal automations and connected accounts are separate from the shared procedure.
How is this different from everyone using their own AI assistant for work?
Individually they get the same answers twice. Here the version someone got right is saved once and improves for everyone, which is the only way the time saved compounds.
Okou also covers workflows and automation, generative services, and Slack. See the built-in web services, the models you can switch between, and pricing.
Give your team one place to keep what works
Reusable workflows and shared results, with each member's access staying their own.
