B2B SaaS User Level Configuration

Aatir Abdul Rauf

By 

Aatir Abdul Rauf

Published 

Aug 7, 2022

B2B SaaS User Level Configuration

If you're building a B2B SaaS product, you probably have encountered this question:

"At what user level do I place this configuration? Should the account admin be able to affect this or should every user have control?"

There are usually 3 flavors to this:

1) Top-down:
Whenever a structure has to be enforced across all users, keep the configuration at the admin level.

For example, the stages of a deal pipeline in a CRM (or recruitment stages in an ATS). Companies would typically want to have a consistent sales process, so the admin regulates this and applies it for all.

2) Hybrid:
Suitable for situations where there is a recommended default by the admin but users are free to override it.

For example, columns of a tabular view of records. The admin can issue a default column set, but users are free to personalize it if need be.

3) Open:
No default is imposed by the admin and users can choose to personalize as they seem fit.

For example, the saved filters on a search. There isn't a defined default and every user can have their own set of filtered views.

Then, you have the gray areas like tags.

Apps like Asana keep it open while others work with hybrid or strict.

The best model depends on your target industry & the diversity of your audience.

Subscribe to Aatir's Newsletter

Weekly Product Management & Marketing Insights in your inbox

Behind Product Lines

The unfiltered truth about the wonders & perils of product management marketing & growth in practice.

Related Posts