Knowledge base
How modules work
Modules are the apps inside your workspace. Install what you need, connect an account, and they start sharing data with each other.
Modules are the apps in your workspace
A workspace on its own is an empty room. Modules are what you put in it. Each module adds a set of pages, a set of abilities, and its own data. The pixel module records site activity. The CRM module keeps contacts. The ads connectors bring in spend and performance.
It works like an app store with two differences. Every module is built or reviewed by Orkie, and most businesses never install anything themselves. Your operator does it during setup and adds more as your needs grow.
Installing a module
Installing takes minutes, not weeks.
- An admin or your operator picks the module from the catalog.
- The module is added to your workspace with its own pages and settings.
- If the module needs an outside account, you connect it (see below).
- The module starts collecting or syncing. Most show useful data the same day.
Nothing about installing one module affects another. You can add the shared inbox this month and Creative Studios next quarter.
What "connected" means
Many modules link to a service you already use: Shopify, Google Ads, Meta, QuickBooks, Slack, YouTube. Connecting means you sign in to that service and grant Orkie permission to read, and sometimes write, on your behalf.
A few things to know:
- You stay in control. The connection uses the service's own approval screen. Orkie never asks for your password.
- Permission is specific. A connector asks only for what its module needs. The ads connector cannot touch your store. The store connector cannot touch your ads.
- You can disconnect at any time. Revoking access stops the sync. It does not delete the data already in your workspace unless you ask for that too.
- "Connected" is visible. Every connector shows whether it is healthy, when it last synced, and whether anything needs attention.
How modules share data
This is where Orkie is different from a pile of separate tools. Modules pass information to each other inside your workspace so each one gets smarter.
Some examples you will see in practice:
- Pixel feeds CRM. When the pixel identifies a visitor through a form, a login, or a purchase, that activity appears on the person's CRM timeline. You see the ad they clicked, the pages they viewed, and what they bought, in one place.
- CRM feeds ad audiences. Build an audience in CRM, such as "bought twice, not in the last 90 days." With approval, that audience can be sent to your ad platforms for retargeting or exclusion.
- Commerce feeds the pixel. Orders from Shopify or BigCommerce confirm what the pixel saw in the browser. Refunds flow back so revenue numbers stay honest.
- Inbox feeds Projects. A customer email that needs follow-up becomes a task in Projects with a link back to the conversation. No copying and pasting.
- Inbox reads commerce. When a customer asks where their order is, the draft reply already knows the order status.
- Everything feeds your AI assistant. Ask a question in Claude or ChatGPT and the answer can draw on any installed module you have permission to see.
Sharing is deliberate and bounded. A module can only see what another module chooses to share. Your data stays separate from every other business. It only goes out to the services you connect, through actions you approve.
Turning things off
You can switch a module off without uninstalling it. Its pages disappear from the menu, its syncs pause, and other modules stop receiving its updates. Turn it back on and it picks up where it left off.
Uninstalling goes further. The module is removed and its data can be wiped on request. Your operator will confirm what is affected before doing it, because other modules may rely on that data.
Two more switches worth knowing:
- Per-user access. An admin can hide a module from specific roles without turning it off for everyone.
- Kill switches. Some abilities, such as AI drafting in the inbox, have a workspace-wide switch that overrides every individual setting. Useful when you want to pause something fast.
Custom modules
If the catalog does not cover a need, Orkie can build a module for you. You describe the job in plain language. Orkie builds it, reviews it, and installs it in your workspace like any other module. See the article on custom modules and integrations for details.
Getting started
Your operator will suggest a starting set of modules on the first call based on how you sell and where you advertise. Talk to us or contact us to talk it through.
Last reviewed 2026-09-20. Something unclear? Tell us and we will fix the article.
See your real numbers.
Talk to us about your business, or call. No pressure, no hard sell. Call 1-877-ORKIE-15.