https://avo.cool logo
Hey there. I'm planning to run a B2B app
# general
b
Hey there. I'm planning to run a B2B app using Avo. Plan is to have one interface for admins and another for business clients where they could create orders, view order info, update settings, etc. I guess for that to work I'd need to somehow separate Avo's scopes to serve different purposes. Do you think Avo would be a good fit for the 'business clients' part? Or should I pursue other custom solutions and let Avo handle only the admin side of the application?
l
oh, it can handle the business clients part!
we have quite a few customers that use Avo as the "front-facing" app for their business
b
Are they utilizing what Avo has to offer or lean more into creating custom views on top of Avo?
I'm planning to have one login form, but 2 separate subdomains for admins and business clients, e.g., admin.b2b.com & app.b2b.com. Both with mostly different views. Perhaps you have any tips going forward from your experience?
l
they started with what Avo offers as those views provide so much value
some have built their own as they needed aftewards
most of the time is for functionality that doesn't really pertain to what Avo does. something very specific to their business
b
Good thing is that I see Avo is pretty customizable if you want to implement your own business logic
l
you'll need to use the authorization feature to show/hide buttons, filter records, and allow access
b
Appreciate your help! I'll try it out
l
definitely!
anytime
we don't yet support custom configurations per sub-domain, but you can use Rails routing to get the effect you need
heads up with two subdomains: this is the only per-seat pricing we do. for two subdomains you'll need two licenses https://avohq.io/faq/one-license-per-url.html
b
Yeah, already figured that out, no probs
l
nice! thanks!