Security
Teammates read, look things up, and draft inside your Slack. Anything that reaches a customer, a vendor, or another tool waits for a person's ok, and every step is written down. Here is how that works, and what happens to your data.
Approvals
A teammate prepares the work. A person decides whether it goes out. The held item sits in the same thread where you asked, with the exact words that will be sent.
Emails, texts, and anything that changes a record in another tool, like an invoice in QuickBooks or a job in Jobber.
Only the person who asked. Everyone in the channel can see the held item, who approved it, and when.
An ok covers the exact draft you saw. If anyone edits it after approval, it waits for a new ok.
Reading the thread, looking things up, and replying inside Slack. Those stay inside your workspace.
@Front Desk send Carol Whitfield the quote for the 3-ton replacement. Use the numbers from Tuesday's visit.
Drafted from job 4471. It's held for your ok, Maria.
Held for your ok Email to Carol Whitfield
Hi Carol, thanks for having us out on Tuesday.
Replacing the 3-ton unit comes to $7,480 installed, including the new pad and thermostat. We can start as early as Thursday the 23rd. Reply here and we'll hold the date.
Maria, Hendricks HVAC
Only Maria can approve this. She asked for it.
A working example. Nothing here is sent.
Audit log
Your team can see what each teammate did and why, in the console and in the thread. Enterprise can export the full log.
Isolation
Threads, channels, workspaces, and companies each have their own boundary. A teammate only knows what it was given in the place it is working.
Thread
A teammate remembers the thread it is working in. What it learns there does not show up in another thread.
Channel
A teammate reads the channels someone added it to. It cannot read other channels, or direct messages between people.
Workspace
Each workspace has its own teammates, routines, spending cap, and history.
Company
Every record is stored under your company and checked on each read and write. A missing record and another company's record get the same answer: not found.
Data handling
Conversation history is deleted after 90 days. Remove CrewOS from Slack and your workspace's data is deleted within 30 days. To delete it sooner, email [email protected].
Day 0 · message posted Day 90 · deleted
Day 0 · removed Day 30 · deleted, at the latest Day 30 · deleted
AI models
To write a reply, a teammate sends the parts of the conversation and tool data it needs to an AI model provider. Our agreements with these providers do not allow them to use your content to train their models.
Enterprise: bring your own model keys. Requests run under your own provider account and your own terms.
Spending caps
You set one monthly spending limit per workspace. When usage reaches it, teammates stop and tell you. Nothing is billed past the cap. Raise or lower it in the console at any time.
Your crew reached this month's $60.00 cap, so I've paused. Nothing more will be billed until Nov 1, or until someone raises the cap.
Sign-in and access
Sign-in to the console runs through WorkOS. Each person has their own account, and their access is set per company. Your role comes from our records, never from anything a browser sends.
Responsible disclosure
If you think you've found a vulnerability in CrewOS, email us before you share it anywhere else. A person reads every report.
Email [email protected]