[Suggestion] Plans Mixing (Std, Pro, Ent) for different users in the same workspace

Ideas & Features
1

Ability to have a mix procurement of varying quantity at different pricing plans.

Use case:
Generally, there are user roles (job functions) that a standard plan solves. But, there are some user roles (job functions) where the features may be better for pro.
Example:
Tech dev teams don’t need much of the strict access template since not much are like highly confidential. But unlike for Sales example, in managing their sales prospects they will highly benefit with the strict access template.

How can it be implement in the workspace?
What we can see is that the pro versions be applied at database-level as always. the configuration can still happen like the user groups where pro users and above can only be visible from the list.

The hardpart?
Even with the the.finbery.io documentation, it is still not updated with all the differences of the plans at each features so, I think the implementation can be done for some time.

2

It is highly unlikely that Fibery will introduce pricing tiers per person or per department or per database.

What info do you think is missing from here:

?

(make sure to view it on a large/wide screen if you want to see the per-feature comparison)

3

it is something like Google/Microsoft where you can purchase multiple tiers of microsoft 365 license/ google workspace licenses. and just delegate which license tier is applied to that user.

Since fibery is already implementing tier pricing but applied in the workspace as a whole, you can just apply it the same and delegate the license type under the users database and applied to the rest of the workspace for that user.

It would make sense for department where a pro/enterprise is appropriate than the standard. Like, for the “Access template”, not all users need that feature, maybe only a handful needs that feature. That also applies to the “Group”, some team members may not use it at all but maybe like a few may need it.

4

I get the principle, but I don’t think it will happen any time soon.

There are many ‘workspace-level’ features that vary across the pricing tiers. For example

  • semantic search limits
  • entity sharing limits for guests
  • ability for automations/buttons to use scripts

etc.

It gets unnecessarily complicated to implement per user pricing for these.

Also, implementing support for plan mixing might reduce the average revenue generated per workspace, which would have to be compensated for by a corresponding per-seat price increase for all customers.