A practical guide to the AI-native workspace, from your first sign-in to automating the work you’d rather not touch. Read top to bottom, or jump to whatever you need.
Scopien is one workspace that holds the four surfaces most teams juggle across a dozen tools, Scopien Chat, Cortex, Projects, and ScopieFlows, unified under a shared AI layer called the Brain. Everything you do in one surface is available to the others, so the assistant you talk to in Scopien Chat already knows about the deal you closed in Cortex and the ticket blocking your launch.
Every object, a contact, task, message, file, is addressable by the same @mention syntax across all surfaces.
Collaborative editing, presence cursors, and instant sync. No “refresh to see changes.”
Your workspace data is isolated. Brain queries run on an instance scoped to your tenant.
Every action in the product is triggerable. If you did it twice, you can automate it.
New here? Skip to the five-minute quickstart below, it walks through the first things most new members do.
You’ll be productive after these five steps. Each takes under a minute.
From the sign-in screen, choose Create workspace, name it something short (Acme, Clarity HQ), and pick a region. You can invite teammates now or later.
In Settings → Integrations, connect Gmail, Slack, or a calendar. The Brain uses this context to make its first useful suggestion in record time.
Try What deals closed last week? or Summarize my Monday meetings. The Brain pulls from your connected sources, not a generic model.
In Cortex, paste a CSV or start from the Sales pipeline template. Five stages, editable anytime. Use ⌘N to add a deal from anywhere in the app.
Open ScopieFlows → New and pick the template “When a deal reaches Proposal, notify me on Slack and create a task.” Done. This one saves most teams an hour a week.
A workspace is a boundary: everyone inside sees each other’s work (unless explicitly private); nobody outside does. Most teams use one workspace per company. Larger orgs sometimes create one per business unit.
Go to Settings → Members and add email addresses. You can choose a role per invite, Admin, Member, or Guest (external, scoped to specific projects).
The Brain is off until you opt a source in. Under Settings → Brain sources, toggle which integrations it can read from. You can also write custom instructions, e.g. “Always format dates as YYYY-MM-DD”, that apply across every Brain response.
Brain config# instructions.md, applied to every Brain responsepersona: "Concise, neutral. No filler."timezone: "America/Los_Angeles"default_format: - dates: YYYY-MM-DD- currency: USD, thousands separatorredacted_terms: ["salary", "personal_email"]
Scopien Chat is where you talk to teammates and to the Brain. Messages to people are regular chat; anything prefixed with /ask or sent in a Brain thread goes to the assistant.
Three icons in the composer control what the Brain can see for any given message:
Every Brain response is followed by a row of source chips, the Cortex records, messages, or files it drew from. Click any chip to open the source in place.
Keep threads focused. The Brain performs best in threads of 20 messages or fewer. Start a new thread for a new topic rather than extending a long one.
The Cortex holds contacts, companies, and deals. Every record is a row in a table you can pivot into a kanban (by stage) or a timeline (by expected close). Custom fields are first-class, add them from the column header.
Stages are just named groupings. Default pipeline: Lead → Qualified → Proposal → Negotiation → Closed. Drag deal cards between stages or use ⌘↑/⌘↓ with a card selected.
Type @ in any field to link to another record. Links are bidirectional, opening a contact shows every deal, message, and task they appear in.
Projects are kanban boards with columns you control. Each card is a task with a title, assignee, due date, priority, and any custom fields your workspace has defined.
Same underlying data, four views:
Kanban columns, default.
Dense table with sort & group.
Gantt-style, for dates and dependencies.
Month or week grid by due date.
An ScopieFlow is when X happens, do Y. Build them visually in the flow editor or describe them in plain English and let the Brain scaffold the flow for you.
Every ScopieFlow has one trigger, any number of conditions, and one or more actions. Triggers can come from any product surface (a new deal, a completed task, a message mentioning a keyword) or from an integration (a Slack reaction, a new calendar event).
flow.yamltrigger:type: "crm.deal.stage_changed"to: "Proposal"conditions: - deal.value: { ">": 10000 }actions: - slack.post_message:channel: "#wins"text: "Deal {{deal.name}} moved to Proposal"- projects.create_task:title: "Send proposal to {{deal.contact}}"due: "+2 days"
Scopien is keyboard-first. These work on every surface.
Scopien connects to the tools you already use. Each integration is bidirectional, reads incoming data and can push outgoing actions via ScopieFlows.
Email threads appear in contact records. Send from inside Scopien.
Mention a deal or task; it links back. Slash commands create records.
Meetings auto-associate with contacts. Meeting notes land in the record.
Link issues to project tasks. Status syncs both ways.
Invoices and payment events flow into Cortex deal records.
For everything else. Trigger flows from any webhook URL.
Workspace data is encrypted at rest (AES-256) and in transit (TLS 1.3). Admins can enable SSO (SAML or OIDC), SCIM provisioning, and audit log export. Brain queries run on a per-tenant inference endpoint, your data is never pooled with other workspaces or used for model training.
From Settings → Privacy you can:
Scopien is unified by design, Scopien Chat, Cortex, Projects, and ScopieFlows share one data model and one AI layer. You’re not bolting four tools together with integrations; the assistant sees everything natively.
No. Your workspace runs on an isolated inference endpoint. Data is never used for training foundation models, and we don’t share your content with any third party.
Yes. We ship importers for Salesforce, HubSpot, Pipedrive, Notion, Linear, and Asana. For anything else, paste a CSV or use the REST API.
Per seat, monthly or annual. There’s a free tier for workspaces of up to 3 members with generous limits. Enterprise pricing is custom.
Yes, REST and GraphQL APIs, plus official SDKs for TypeScript and Python. ScopieFlows can call any public HTTPS endpoint. See Settings → Developer for tokens and docs.
US-East by default. EU and AP regions available on Business and Enterprise plans. You pick region at workspace creation; data never crosses regions without explicit export.