The connected platform

Many possibilities. One shared core.

A social community, a support system and a world of opportunities, connected through one member identity.

Pre-launch edition · 3 min read · Updated October 2026
The idea, in focus

The planned platform connects member experiences with the people and tools needed to run them. Shared identity, permissions, reference numbers and activity records make continuity possible.

Inside the connected system

One request.
A whole community behind it.

Follow a planned support journey. See how a member, service teams and an agreed provider connect without losing responsibility.

01 / A private concern starts with a choice.

A member begins.

The member describes the issue, chooses a safe contact method and decides what to share. The planned intake separates an urgent concern from a routine request.

Responsible participant
Member
What connects the work
A private request
02 / The desk connects the need to expertise.

The right route becomes clear.

Triage checks scope and urgency. A reference links the request to a lead officer; connected needs can involve another team without losing the main owner.

Responsible participant
Service desk
What connects the work
An assigned pathway
03 / A wing turns the request into actions.

People coordinate the work.

The responsible officer records the next action, gathers only relevant information and coordinates linked tasks. A supervisor can review waiting or overdue work.

Responsible participant
Service wing
What connects the work
Actions and updates
04 / A referral travels with permission.

Specialist support joins the journey.

Where an appropriate arrangement exists, a professional or institution receives the agreed information. Its reference links to the original request, while its decisions remain its own.

Responsible participant
Agreed provider
What connects the work
A linked referral
05 / Closure needs a clear explanation.

The member sees what happened.

The outcome distinguishes support completed, partial progress, onward referral or another stated reason. The member can confirm what helped and ask about review.

Responsible participant
Member + officer
What connects the work
An explained outcome
06 / Useful patterns inform better service.

Experience improves the system.

Suitable aggregate findings help teams update a guide, improve training or change a process. Personal case details do not automatically become public reports.

Responsible participant
Review team
What connects the work
A service improvement
Planned workflow illustration · No live case dataExplore the operating system
The system, illustrated

A common foundation. Distinct experiences.

Shared identity and permissions connect the platform; each service retains its own purpose.

01

Connect

Profiles · Groups · Pages

Public participation and chosen visibility

02

Grow

Learning · Careers · Enterprise

Useful knowledge and relevant opportunities

03

Get support

Desks · Wings · Referrals

Private requests and accountable follow-up

CONNECTING PRINCIPLE

Member ID · Consent · Scoped access · Shared references

On this page
01

Connection and belonging

Profiles, groups, pages, messages and events help members discover people with shared interests, skills or experience.

02

Support with continuity

Get Help turns a concern into a private request with a reference, responsible officer, recorded actions and an outcome.

03

Learning and opportunity

Jobs, mentoring, skills exchange, professional discovery and enterprise connections help members develop and contribute.

04

People behind the platform

The CRM, Workspace, Meet, Approvals and ERP connect service work, team coordination and resource management.

05

Intelligence and knowledge

Rahnuma provides planned assistance with language and information. Media and reviewed resources help useful knowledge travel across the community.

06

Access across different needs

The planned model includes web and mobile experiences alongside lighter, voice and assisted channels. Each channel will open according to readiness.

A practical example / Planned experience

One identity, connected experiences

01

The starting point

A member joins a professional group, finds a mentor and later asks for support.

02

How the parts connect

The planned shared core retains the member’s identity while each service uses only the information it needs.

03

What useful progress means

Continuity across the platform without turning every interaction into public information.

Explore the connected pathway
How the parts connect

A clear path through the experience.

  1. 01One identity
  2. 02Relevant connections
  3. 03Useful services
  4. 04Accountable follow-up

Find your way.

Search the community, services, wings and practical questions.

Esc to closeExplore all pages →