Skip to content
Journeybee Help Center home
Journeybee Help Center home

Partner Portal - Room Types

Overview

Partner portals organise partnership activities into "rooms" - distinct workspaces for different functions. This guide describes all available room types.

Room Categories

Pre-defined Rooms - Standard rooms with built-in functionality. Each can exist once per partner type.

Custom Rooms - Flexible rooms you build with blocks. Create unlimited custom rooms per partner type.

Pre-defined Rooms

Overview

Purpose: Partnership dashboard showing performance and activity

What's Included:

  • Performance metrics (leads, deals, commissions)

  • Quick action buttons

  • Recent activity feed

  • Partnership announcements

  • Customizable widgets

Best For: Landing page, morning check-in, quick status

Example: "Mike logs in Monday and sees 3 new deal updates, $15K pending commissions, and a new training module. He clicks 'Submit Lead' before his 9am call."


Leads

Purpose: Submit and track lead referrals

What's Included:

  • Lead submission form

  • Status tracking (new, qualified, demo, proposal, closed)

  • Lead history

  • Commission amounts

  • Notifications

Best For: Referral programs, lead generation partnerships

Example: "Sarah submits a conference lead. Two weeks later, she gets notified it moved to demo stage."


Deals

Purpose: Monitor sales opportunities and revenue

What's Included:

  • Deal pipeline

  • Stage tracking (proposal, negotiation, closed)

  • Revenue and commission display

  • Deal notes

  • Win/loss tracking

Best For: Reseller programs, sales partnerships

Example: "Carlos sees 5 active deals worth $250K. One moved to negotiation, so he adds a note about competitor pricing."


Resources

Purpose: Training, marketing, and sales materials

What's Included:

  • Document library with folders

  • Search and filtering

  • Version control

  • Download tracking

  • Categories (training, marketing, sales, technical)

Content Types:

  • Training materials and certifications

  • Marketing assets and templates

  • Sales tools and battle cards

  • Technical docs and API guides

  • Program updates

Best For: All partner types, self-service enablement

Example: "Jennifer needs a healthcare case study. She filters by 'Healthcare' and 'Case Studies' and downloads the PDF for her proposal."


Projects

Purpose: Collaborative project management

What's Included:

  • Project timelines

  • Task tracking

  • Team collaboration

  • Progress monitoring

  • Deliverable upload

  • Comment threads

Best For: Implementation partnerships, joint initiatives

Example: "ABC Corp sees their onboarding is 75% complete. They have 3 tasks this week: upload config, complete UAT, schedule go-live. They upload the file and mark it done."


Messages

Purpose: Direct communication with partner managers

What's Included:

  • Direct messaging

  • Conversation threads

  • File attachments

  • Message history

  • Notifications

Best For: All partner types, reducing email

Example: "Tom asks about a lead from last week. Within 2 hours, his partner manager responds with the status."


Brand Guidelines

Purpose: Brand assets and usage rules

What's Included:

  • Logos (multiple formats)

  • Brand colours and typography

  • Design templates

  • Usage guidelines

  • Co-branded materials

Available Formats:

  • High-res logos (PNG, SVG, EPS)

  • Templates (PowerPoint, Google Slides, Canva)

  • Brand guide PDF

  • Social media graphics

  • Print files

Best For: Co-marketing partnerships

Example: "Lisa downloads the co-branded PowerPoint template for a joint webinar presentation."


Shared Files

Purpose: Document collaboration and exchange

What's Included:

  • File upload/download

  • Folder structure

  • Version control

  • Access monitoring

  • File comments

Common Files:

  • Contracts

  • Proposals

  • Technical specs

  • Project docs

  • Spreadsheets

Best For: Contract management, project partnerships

Example: "Partner uploads signed agreement. Manager uploads countersigned version. Both have access to final contract."


Contacts

Purpose: Partnership team directory

What's Included:

  • Partner team listings

  • Internal team info

  • Roles and responsibilities

  • Contact details

  • Team notifications

Displayed Info:

  • Name and photo

  • Role and title

  • Email and phone

  • Location

  • Responsibilities

Best For: All partner types, team clarity

Example: "New team member looks up who handles deal registration, technical support, and marketing."


Distributor Partners

Purpose: Sub-partner management for distributors

Available For: Distributor partner type only

What's Included:

  • Sub-partner directory

  • Performance metrics

  • Aggregate pipeline

  • Onboarding tools

  • Compliance tracking

  • Resource distribution

Best For: Two-tier programs

Example: "Distributor XYZ manages 25 sub-partners. They see 3 in onboarding, monitor network performance, and distribute new training materials."


Custom Room Patterns

Build these using blocks:

Training Portal

Blocks:

  • Text: course descriptions

  • Videos: training modules

  • Tasks: completion tracking

  • Goals: certification progress

  • Documents: course materials

Use For: Certification programs, enablement


Campaign Center

Blocks:

  • Text: campaign briefs

  • Images: campaign creative

  • Documents: campaign assets

  • Action Bar: campaign tools

  • Analytics: performance

Use For: Joint marketing, launches


Support Hub

Blocks:

  • Text: FAQs

  • Documents: troubleshooting guides

  • Embed: support ticket system

  • Videos: tutorials

  • Introduction: support team

Use For: Technical support, enablement


Analytics Dashboard

Blocks:

  • Analytics: key metrics

  • Embed: external dashboards

  • Goals: target tracking

  • Text: metric explanations

Use For: Executive reviews, scorecards


Onboarding

Blocks:

  • Text: welcome messages

  • Introduction: team intros

  • Tasks: onboarding checklist

  • Videos: getting started

  • Action Bar: next steps

Use For: New partner activation


Choosing Rooms

Ask yourself:

  1. What do partners do daily? → Include those rooms

  2. What info do they need? → Provide relevant resources

  3. How do they communicate? → Enable communication rooms

  4. What's unique about your program? → Build custom rooms

  5. What stage are they in? → Progressive access

Start with:

  1. Overview

  2. Leads or Deals

  3. Resources

  4. Messages

  5. 1-2 custom rooms

Add more as you learn what partners actually use.

Example Configurations

Minimal (3-4 rooms): Overview, Leads, Resources, Messages

Standard (5-7 rooms): Overview, Leads, Deals, Resources, Brand Guidelines, Messages, Contacts

Advanced (8+ rooms): All relevant pre-defined rooms + 2-4 custom rooms with progressive access

Daily Partner Workflows

Morning Check:

  1. Overview - metrics and updates

  2. Messages - new communications

  3. Leads/Deals - pipeline changes

Before Customer Meeting:

  1. Resources - case studies, sales tools

  2. Brand Guidelines - presentation templates

  3. Deals - opportunity details

Submitting Business:

  1. Leads - submit referral

  2. Deals - register opportunity

  3. Messages - notify manager

Monthly Review:

  1. Overview - monthly performance

  2. Deals - pipeline health

  3. Custom analytics room - deep dive

Quarterly Business Review:

  1. Overview - quarterly summary

  2. Deals - revenue analysis

  3. Custom executive room - strategic planning

  4. Shared Files - QBR documents

Best Practices

Room Selection:

  • Start essential only

  • Add based on actual needs

  • Remove unused rooms

  • Monitor usage

Room Naming:

  • Clear, descriptive names

  • No internal jargon

  • Partner perspective

  • Consistent across types

Room Organisation:

  • Most important first

  • Group related rooms

  • Logical flow

  • Use custom rooms for gaps

Content Management:

  • Keep focused

  • No duplication

  • Update regularly

  • Archive outdated content

Access Control:

  • Default to open

  • Restrict strategically

  • Test partner views

  • Document restrictions

Next Steps