Client Portals and Dashboard Systems · Lesson 10 of 12

Franchise and Parent-Child Location Views

Plan how portals should behave when one account supervises multiple child locations or teams.

Academy Plus 4 practice exercises 1 homework item

What you will learn

  • Explain how parent-child account structures change portal visibility and navigation.
  • Design location switchers and rollup views that keep the active location clear.
  • Apply location-scoped permissions to dashboards, documents, tickets, and actions.
  • Plan cross-location escalations without leaking one location's private context to another.

Lesson shape

28 minute lesson with 6 sections, 4 exercises, 5 checkpoint questions, and 1 homework submission.

This track requires the Academy Plus plan.

Lesson outline

What this lesson includes

This lesson is available with the Academy Plus membership. Create an account to open the full student player, exercises, quiz, and completion tracking.

Overview

Model the account hierarchy first

Full lesson content unlocks in the student player.

Explain

Keep the active location obvious

Full lesson content unlocks in the student player.

Explain

Separate location views from rollups

Full lesson content unlocks in the student player.

Practice

Apply location-scoped permissions

Full lesson content unlocks in the student player.

Explain

Design cross-location escalation paths

Full lesson content unlocks in the student player.

recap

Review the multi-location portal path

Full lesson content unlocks in the student player.

Homework

Assignments attached to this lesson

Text response

Write a parent-child location portal note

Choose one franchise, branch, regional, or parent-child account situation. Write four short notes that name the parent-child account structure, location switcher behavior, rollup view, and location-scoped permission rule.

Not started

Open homework