Using SmixAI for your business
How one organisation runs SmixAI for itself — connect your own systems, invite your own people, and turn findings into approved fixes and measured savings.
Overview
This guide is for one organisation using SmixAI for itself: your systems, your people, your requests. If you are an agency or partner running SmixAI on behalf of several clients, read Using SmixAI for your customers instead. The two guides are written so that you can follow either one without the other.
Everything you do belongs to your organisation. Members, connections, findings, agents and billing live under it, and its data is isolated from every other organisation's.
What you will do
The whole product follows one loop: Connect → Scan → Discover → Recommend → Act → Measure. In your own business that becomes four steps.
- Set up your organisation and invite your people.
- Connect your systems and scan them.
- Review what SmixAI found and decide what to fix.
- Work requests and measure the savings.
1. Set up your organisation and your people
On first sign-in SmixAI places you in an organisation. Invite teammates and give each a role:
| Role | What it is for |
|---|---|
| Viewer | Reads results; cannot change anything |
| Member | Works requests, runs scans and discovery |
| Admin | Manages members, connections and settings; approves writes to connected systems |
| Owner | The organisation lead and billing contact |
Give people the least access that lets them work. Inviting members uses your sign-in provider's organisations feature.
2. Connect your own systems
SmixAI connects to the systems you already run. Today these are live: Salesforce, GitHub, Google Workspace (Gmail), Priority ERP, MuleSoft Anypoint, Postman and monday.com; others are in preview or planned. See What is SmixAI? for the current list.
Connections have three levels: a System you own, an Environment inside it (production, sandbox, developer…) and the encrypted Credential for that environment. Connect a sandbox before production so you can try things safely, and use a dedicated, least-privilege user rather than a personal login.
SmixAI reads configuration and counts — not your customer records. Run a scan to inventory each environment.
Not ready to connect anything? Load demo data to explore a realistic sample organisation first, and remove it any time.
3. Review what SmixAI found
Run Discovery. Each finding has a severity, a confidence score and the evidence behind it, and each comes with a recommended fix and an estimated return. Every figure is a real count multiplied by a stated assumption, never a guess. Accept the recommendation for a finding you want to act on, or dismiss it; your organisation health grade (A–F) summarises what is still open.
4. Work requests and measure the savings
Your people raise requests — cases, tasks or transformation work — and an AI resolver diagnoses them and proposes a fix.
- Nothing is applied on its own. By default a fix is a proposal that a person approves.
- Writes to connected systems are separate. An admin reads the field-by-field before and after and approves it; there is no bulk approve, and a proposal expires if nobody decides.
- Agents start in shadow. A new agent proves itself against real human outcomes before it is allowed to act on its own.
- Measure. The dashboard tracks the value you have captured over time.
Keeping it under control
- Roles decide who can see which pages; admins can narrow them further.
- Significant actions are recorded in an audit log: who did what, and when.
- Where multi-language is switched on for your workspace, admins choose the organisation's default language, English or Hebrew, and members can pick their own.
A sensible first week
- Day 1 — sign in, explore demo data, invite two or three people.
- Day 2 — connect one sandbox environment and run a scan.
- Day 3 — run discovery and read the top findings together.
- Day 4 — open a request for the most valuable finding and review the proposal.
- Day 5 — approve one fix, then check the dashboard.
Next steps
- Quickstart — your first ten minutes.
- Key concepts — the vocabulary.
- Using SmixAI for your customers — if you also serve clients.
- Roles & permissions and Organizations & multi-tenant model.