Using SmixAI for your customers

Overview

This guide is for a partner: an organisation that uses SmixAI for other organisations — an implementation partner, an agency, a managed-service provider. You run the work; your clients are the ones it is done for. If you are one organisation using SmixAI for itself, read Using SmixAI for your business instead. The two guides are written so that you can follow either one without the other.

SmixAI supports two ways of serving clients. Choose one per client relationship; the rest of this guide says what changes between them.

	Clients as records (partner program)	One organisation per client
Where the client lives	A record inside your organisation	Its own SmixAI organisation
Who signs in	Your team only — nobody at the client signs in	Your team, plus whoever the client invites
Connected systems belong to	Your organisation	The client's organisation
Data separation	Between your clients, by the client on each request	Between organisations, enforced on every query
Billing	Yours	Per organisation
Best when	You do the work and the client only needs the outcome	The client must see, own or administer its own workspace

The partner program: clients as records

A partner is an organisation that keeps a list of its own clients and opens requests for them.

• A client is a record, not a workspace. It has a name, an optional Client ID (your own account number for it) and an industry. It is not a separate SmixAI organisation, and nobody at the client signs in.
• Your team works the request as any other. The request simply says which client it is for, and shows the client's name as its requester so it is clear who it is for.
• Everything stays inside your organisation. A client's requests are never in another organisation. Separation between two of your clients is by the client named on each request: filter the Requests list by Client, or open the client's own page to see only its requests.
• A partner is set up by the SmixAI team. Ask your SmixAI contact if your organisation should be a partner. Organisations that are not partners see no client fields anywhere.

Adding and managing clients

1. Open Clients in the sidebar (under Operate).
2. Select Add client, enter the Client name, and optionally a Client ID and an Industry.
3. You become the client's contact, and a new client starts Active, so it can be picked straight away.

Owners and admins can always add, edit and archive clients; viewers never can; members can only read the list unless an owner or admin allows them to edit. Archive a client you no longer work with: its requests stay, and it can no longer be picked for a new request.

Your agreement with SmixAI may set a number of clients. Active and inactive clients count against it; archived clients do not.

Opening work for a client

• In the app, New request shows a Client field. Pick the client, or leave No client for work your organisation opens for itself.
• From a client's page, New request for this client opens the form with the client already chosen.
• Through the API, an integration sends the client on the request it creates, and can list one client's requests.
• A SmixAI agent that you download can be given a default client, so the requests it files are for that client.

One organisation per client

When a client needs its own workspace, create it as its own organisation from the organisation switcher. Each organisation has its own members, connections, findings, agents and billing, and its data is isolated from every other organisation's on every query. You switch between the organisations you belong to; the client invites its own people and sets their roles.

Who holds the credentials

Connected systems follow the organisation they are connected in:

• Clients as records: the connections are in your organisation, so you hold the access. Use a dedicated, least-privilege user in each client's system rather than a personal login, and rotate credentials periodically.
• One organisation per client: the connections are in the client's organisation. The client can see, reconnect and remove them.

In both models SmixAI encrypts credentials at rest, scopes every query to an organisation, and records significant actions in an audit log. SmixAI reads configuration and counts — object and field definitions, automation, licence and storage usage — not your clients' customer records. See Security & data handling.

What a client can and cannot see

• Client as a record: nothing in SmixAI — it has no sign-in. What it receives is what you send it.
• Client with its own organisation: only that organisation, according to the roles you set. Viewers can read, members can act, admins and owners manage access.
• Neither model shows one client another client's data. Clients as records are kept apart by the client on each request; separate organisations are kept apart by tenant isolation.
• If your clients' own customers need a self-service page, an App Studio customer portal is a separate surface with its own isolated sign-in.

How work is handed back

SmixAI proposes; a person decides.

1. A request is opened, for a client or for your own organisation.
2. SmixAI diagnoses it and drafts a fix. By default this is propose-only — nothing is applied.
3. A person on your team (or the client's, in the one-organisation model) reads the proposal and approves, rejects or sends it back with a question.
4. A change to a record in a connected system is a separate, admin-approved step. It shows the field-by-field before and after, and it expires if nobody decides.
5. The outcome is written to the request's timeline, so you can show a client what was done and why.

Getting started

1. Decide the model for this client.
2. For clients as records, ask your SmixAI contact to enable the partner program, then add the client.
3. Connect the client's systems with a least-privilege user, run a scan, and run discovery.
4. Open the first request for the client and review what SmixAI proposes before approving.

Next steps

• Using SmixAI for your business — the direct model.
• What is SmixAI? and Key concepts.
• Partner program — clients and Organizations & multi-tenant model.