Troubleshooting & Tips

Clarify your layout setup

4min

Here are some questions to build your app's layout structure and plan content.

It's recommended to use multiple layouts when:

  • The content for Groups varies across more than one or two sections of the layout.
  • You have totally different sets of users. For example, clients versus employees.

Yes, you can use the same layout across multiple Groups or Teams if the content and features are the same or similar. If there are minor differences, you can either:

  • Use sets to tailor specific sections for each Group/Team or User tag; or,
  • Vary the content in a section by selecting different availability.

Sets allow you to customize a section for users by assignment, whether Groups, Teams, or with User tags. This allows you to adjust the layout and place blocks to fit what those users need to see.

It's recommended to use sets if:

  • Most of your content will remain the same and only one part of your design will change, within a larger layout that stays consistent.

You don't need sets if:

  • You're aiming for a completely different experience for totally different users. Instead, you'll want to create a new layout at that level, whether Group or Team. See multiple layouts.

No, sets are not required if you only want to control the availability of content (e.g., Forms, Focus Content, Sequences, Media, Marketplace) within a section. You can manage content availability without needing to create sets.

If you delete a Group or Team layout that’s currently in use, the layout will revert to the organization top-level layout, until you add another one.

There’s no strict limit on the number of sections in a layout, but it’s best to keep the layout streamlined and user-friendly. Avoid overwhelming users with too many sections and focus on content that’s most relevant to them.



  • Most of the layout is the same for everyone, but you need to customize one or two sections.
  • You want to vary the Menus or Feature blocks within a section, whether by Group, Team, or User tag. For example, you want to make the the Health Plan available to one Group but not another.
  • You have a lot of content differences across Groups/Teams and User tags.

You don't need sets if:

  • If it's just a couple of content differences within a section. In this case, you can select content availability without creating sets.

Where as if you want a completely different experince then you create a new layout at that level. This is the traditional way - more when you have totally different users - can only change branding along with the group segments - and editability - admin permisson of it



NOTE: If layout is set up at the org level - you make an admin of group A not org level - can't edit layout