Follow

Introduction to Client Partitions

The commercial purpose of client partitions is to allow you to sell your project as a service. This is made possible because each client can run their experiences independently of the others. Commercial restrictions do apply and any author wishing to sell their projects as a service should contact Sales.

It is important that you design your project to run with partitions as certain triggers such as Date and Time triggers cannot determine which partition to operate with and hence will affect the whole project.

Let’s review the terminology:

Author - that’s you! You’re the project creator; the person registered with Conducttr and who has access to the project to create an experience

Client - the person who licenses the your experience without knowing anything about Conducttr; she does not have access to Conducttr

Audience - the end-user of the experience.

You can create a project and then license it to run for different clients independently of each other. The client is responsible for managing their own audience (although you can see all audience).

All Audience, Groups, Teams and Attributes function as self-contained to that client partition such that if Client A sends a broadcast message to all audience, it is only sent to all audience of the same partition and not to audience belonging to Client B or C etc.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments