One Platform, Many Programs: Running Mentoring Across Teams, Chapters, and Client Organisations

Few organisations run just one mentoring program for long. A company starts with graduates, then adds new managers, then a reverse mentoring pilot for the leadership team. An association starts with early-career members, then adds a program for members sitting a professional exam, then gets asked by its state branches for their own. A training provider starts with one client and soon has five.

Running several programs is where manual approaches fall apart, and where the structure of your platform starts to matter. This guide covers how to run multiple programs inside one workplace, when to use separate workplaces instead, and how to keep people, mentors and data in the right place. It is written for L&D leads in multi-site companies, associations with chapters or branches, and partners who host mentoring for client organisations.

When one program is not enough

Signs you have outgrown a single program:

• Different groups need different mentors, and showing everyone to everyone causes confusion.
• Different groups need different resources, goals or enrolment rules.
• Different parts of the organisation want their own branding, or their own administrators.
• You are reporting to more than one leadership team, board or client.

The first two are usually solved with programs inside one workplace. The last two may call for separate workplaces. MentorPlace supports both.

Programs inside one workplace

In MentorPlace, programs are the organisation’s cohorts or initiatives, such as a graduate scheme, a leadership circle, a new-manager program or a peer network. Each program has a name, summary, longer content, logo, banner, and a status of draft, published or hidden.

Each program can hold its own learning and reference resources, and only published resources are shown. Administrators can define goal templates for a program, with tasks and subtasks, so each cohort starts from the journey the organisation intends.

Cohorts are modelled as programs. There is not a separate cohort object with its own timetable, so if you run intakes, set each one up as a program, such as “Graduates 2026”.

Keeping mentors visible only to the right people

If every member can see every mentor, a graduate may end up booking time with the chief financial officer who signed up for the leadership circle. Programs fix that.

When directory grouping is turned on, mentor discovery respects shared program membership, so people only see mentors who share a program with them. Global programs that the organisation does not own can be hidden, so the catalogue only shows what the organisation published.

For an internal program, the directory can also be limited to the organisation, with cross-organisation and public marketplace browsing switched off.

Enrolment rules per program

Each program can have its own way in.

• Self-enrolment. People can be allowed to enrol themselves, which suits open programs such as career mentoring.
• Auto-enrolment. A program can enrol nobody automatically, every new member, mentors still awaiting approval, or mentors once they are approved. A buddy scheme for new starters might auto-enrol every new member.
• Administrator enrolment. Administrators can enrol and unenrol people directly, which suits invitation-only programs such as a leadership circle.

Administrators can email everyone enrolled in a program, so each cohort can get its own kick-off and check-in messages.

Separate workplaces for regions, chapters or clients

Sometimes programs are not enough. A region may need its own brand. A client should never see another client’s people. A state branch may want its own administrators and its own reports.

For these cases, MentorPlace supports a hierarchy of organisations. A parent organisation can own child organisations, and a partner can host programs for organisations it manages. Each organisation has its own workplace, with its own brand, settings, people and programs. Data is separated by organisation, including matching, so a suggestion for one organisation never returns another organisation’s people.

Reporting runs for each organisation over a date range, so plan to produce one report per workplace. For partners reselling mentoring to clients, prepaid slots can gate the creation of child organisations or users. Our guide to offering a branded mentoring platform covers that model.

A rough rule of thumb:

• Same brand, same administrators, different groups: use programs.
• Different brand, different administrators, or data that must stay apart: use separate organisations.

People who belong to more than one organisation

Some people will need to be in more than one place. A senior mentor might support both a national program and a state chapter. A consultant might work across two client workplaces.

In MentorPlace, a person can belong to more than one organisation and switch between them. Account recovery includes finding which organisations an email address belongs to.

Messaging each program

Several programs means several audiences, and a message meant for the graduate cohort should not land with the leadership circle.

Administrators can message everyone enrolled in a program, so each cohort gets its own launch note, mid-point reminder and wrap-up. Alongside that, the platform sends the emails people expect, such as mentor approval, expressions of interest and session reminders, along with two engagement notes for members who have gone quiet. Each organisation sets its own logos for email, so messages from a child organisation carry that organisation’s brand. Chat can be switched on for the whole organisation where people want it.

A simple rhythm for each program:

1. A welcome message when the program opens, explaining what it is for and how to find a mentor.
2. A check-in after the first month, with a reminder to book the next session.
3. A wrap-up message at the end, with a note on what comes next.

Administrator permissions by area

As programs multiply, so do the people helping to run them. You will want a volunteer coordinator to manage mentors without seeing reporting, or a client administrator to manage their people without touching webhooks.

MentorPlace has organisation administrators and organisation super-administrators. Administrator actions are permission-scoped, and access can be granted separately for areas such as people, mentors, programs, connections, reporting, webhooks and categories. Administrators can be invited, updated, removed and reinvited.

Permissions are granted by area rather than by individual program, so if two programs need completely separate administrators, that is a good sign they belong in separate organisations.

Putting it together

A typical set-up for an organisation running several initiatives:

1. One parent organisation for the central team.
2. Child organisations for each region, chapter or client that needs its own brand or its own data.
3. Inside each, programs for each initiative or intake, with their own resources, goal templates and enrolment rules.
4. Directory grouping turned on wherever mentors should stay within their program.
5. Administrators with access limited to the areas they look after.

Start simple. One workplace with two or three programs covers most organisations for their first year. Add child organisations when a group genuinely needs its own space.

Related reading

• Internal Mentoring Software: What It Should Do, and What to Check Before You Buy
• Mentoring as a Member Benefit: How Associations Use It to Lift Renewals
• How to Build a Mentoring Program That Lasts Past Month Three

See programs and workplaces in action

We can show you programs, enrolment rules and program-scoped directories, and how parent and child organisations fit together. Book a demo.