CRAIM
Start free

Project Transfer To A Client

How an integrator hands a finished project to the client's workspace: the offer, acceptance, what changes at that moment, and what can stop it.

← Back to knowledge base

A workspace holds projects; each project is one company with its own employees, channels, deals and conversations. A project transfer moves one project from your workspace to another person's, and makes them its owner and payer. It is built for integrators who set CRAIM up for clients, but any workspace owner can use it.

Who can do what

  • Request a transfer: an owner of the workspace the project is in.
  • Accept a transfer: the person whose verified account email matches the address in the offer, into a workspace they own.
  • Cancel a transfer: the owner who requested it, any time before acceptance.

Sending the offer

  1. 1Open your workspace home, the page that lists your projects.
  2. 2Press Transfer to a client on the project.
  3. 3Enter the client's email address and confirm.

The offer is valid for seven days. Until it is accepted, nothing changes: you remain the owner and the payer, and the project keeps working. Sending a new offer for the same project cancels the previous one.

The platform does not email the client. Tell them yourself.

Accepting the offer

The client signs in to CRAIM with the account whose email you entered. The email must be verified. On their workspace home they see Project transfers with the offer, and press Accept project. Before confirming they choose:

  • The destination workspace, which must be their own. It cannot be the workspace the project is leaving.
  • Keep the integrator as a technical administrator of this project. When ticked, the sender is added to the project as an administrator, without access to the destination workspace's billing or other projects.

What is checked before anything moves

  • The destination workspace has an active or trial subscription. Without one, the acceptance is refused with a message to choose a plan first.
  • The destination plan's limit on active AI employees fits the project's published employees plus the ones already active in that workspace.
  • If the integrator is kept, the destination plan has a seat for them, unless they are already a member there.
  • The project is idle: no AI task queued or running, no call in progress, no message delivery in flight. Otherwise the acceptance waits with a message to let them finish.
  • The sender is still an owner of the source workspace, and the project is still there.

If any check fails, nothing moves and the message states the reason.

What happens at acceptance

All of the following happen together, stamped with one moment:

  • The project's owner becomes the client, and every owner of the destination workspace becomes an owner of the project.
  • Every previous member of the project is suspended. Pending invitations to the project are revoked.
  • Every active session in the project is signed out.
  • If the box was ticked, the sender is re-added as an administrator of the project.
  • The billing period for the project closes in the source workspace and opens in the destination one. Model usage from then on is charged to the destination balance.

The project itself is not copied or altered: AI employees, knowledge, catalogue, channels, deals, conversations, processes and their history stay in place.

After the transfer

  • The client can transfer the project again, including back to the sender, the same way.
  • Trial eligibility does not travel. Each email address receives one trial, ever.
  • If a retry hits an acceptance that already completed, the same result is returned rather than a second transfer.

See also