Setting Up Manager Hierarchy: Migrating from a Flat Org

Last updated: May 25, 2026

You currently have teams but no hierarchy; everyone sees everything, there's no folder sharing, and there are no visibility settings.

Your existing users, teams, bots, and folders are all preserved — you're just adding structure on top of what's already there.


What changes when Manager Hierarchy is turned on

  • Calls become scoped based on each role's visibility setting

  • Folders and bots follow sharing rules instead of being visible to everyone by default

  • Each user's team determines what they can see


Migration steps

Step 1: Restructure your teams into a hierarchy

Refer: 📄 How to: Set Up a Team Hierarchy

Your existing teams become the foundation. You'll nest them under parent teams to match your org structure.

Step 2: Configure visibility settings

Refer: 📄 How to: Configure Visibility Settings

Decide what admins see and what members see. This is the first time you're setting these; recommended defaults are shown in the article.

Step 3: Review folder and bot sharing

Once Manager Hierarchy is on, folders are visible to everyone unless you restrict them. Go through your existing folders and set sharing as needed.

See the folder sharing section in 📄 How to: Manage Folder and Bot Access


Need help?

Reach out via the chat button or email support@hyperbound.ai.