Best explanation of Sub-User mode vs Multi-User mode distinction?
-
Hi, I plan to set up this plugin, but as your FAQ strongly recommends an upfront selection of either Multi-User or Sub-User mode, I want to understand the difference. I don’t spontaneously find a deeper description than this one on your main page:
“? Sub-User mode: multiple separate accounts grouped together under one parent account (e.g. Holding Company).
? Multi-User mode: multiple users have access to a same master account (useful in case of Corporate Accounts).”Can you point me to a more detailed description of the distinction? To describe it clearer, could it make sense to talk about it with a distinction between the technical account (who logs in) on my platform, versus the commercial account (what department on the customer side becomes committed to pay)?
In my case, I mainly seek to let different individuals perform orders on their company’s aggregate commercial account with us, but with that traceability of who placed each order. (We are small-scale B2B, so the functionality for their coordinator to self-service their individual user accounts is a nice bonus but not critical; it wouldn’t take much time for us to do it for them in personal calls.) At first look, my use case seems to fit your one-sentence description of the Multi-User mode. On the other hand, it seems your admin interface has a system-level switch by which all users in Sub-User mode would have their billing address (thus, commercial account) forced to be their entity’s (technically its “manager’s”). (That, too, looks like it would do the job for my use case. It seems inflexible in the sense that it excludes any possibility of any individual going with a custom billing address for any order, but in my case, I don’t foresee having any need for such flexibility anyway.)
Can you suggest I move forward based on my assumption that a Sub-User mode setup, with forced billing address inherited from manager’s, will do the job in my case?
The page I need help with: [log in to see the link]
- You must be logged in to reply to this topic.