What a customer site is

If you sell training to other organisations, you can give each of them their own Grapevine site rather than putting their people onto yours.

Their own address, their own name and logo, their own learners, their own administrator. From their point of view it is their site; they need not know it is part of a larger network.

Why do that rather than enrol them on yours

• Their learners stay theirs. Their staff list is not mixed into yours, and their administrator manages it without seeing your other customers.
• It is their site. Their branding, their pages, their course list — not yours with their people in it.
• They can run it. Adding people, marking work and watching progress are theirs to do, which is usually what they wanted when they bought training for fifty staff.

The trade-off is that a course they have is a copy of yours, not a window onto it — see Keeping a resold course up to date.

What stays yours

• You create the site and can administer it.
• Courses you copy to it came from you, and Grapevine records that — which is how billing knows whose course it is. See Which site is billed for a course.
• The commercial relationship. Grapevine does not bill your customer; it bills you, and what you charge them is between you and them.

What becomes theirs

• Their learners and enrolments.
• Their copies of the courses, which they can edit.
• Their own Stripe account, if they are going to charge their own people.

Is this right for every customer?

No. An organisation buying fifty places on one course does not need a site — sell them an invitation and let their people use it. See Invitations: selling places in advance.

A customer site is worth it when they want to run training rather than take it: their own catalogue, their own people, over time.