21 posts
When an organization sells through our platform, the money should land in its own account. Here is how connected accounts, platform fees, refunds and...
Some organizations run more than one website. Here is how our platform keeps each site's pages, forms, files and domains separate inside a single acco...
Caching makes pages fast, but a shared cache can also show one customer another customer's data. Here is how we name cache keys so that can never happ...
Permissions only protect people when they are understandable. Here is how we keep roles simple, map them to real responsibilities and handle ownership...
VoVo serves many organizations from one shared database. Here is how every record knows its owner, how queries stay inside the right account and where...
Every organization on our platform has its own look. Here is how theme tokens let each site keep its brand while sharing the same building blocks unde...
Two organizations can both have a page called About. Here is how composite unique keys keep addresses unique inside each account without blocking othe...
VoVo brings websites, membership, email, courses, events and more into one account. Here is why sharing one login and one database makes those modules...
When we publish pages, settings or articles for a website through code, the change runs once, checks its assumptions and never overwrites what the own...
In a platform serving many organizations, turning a feature on is not one decision. Here is how platform switches, plan permissions and customer opt-i...
Sometimes our team needs to see what a customer sees. Here is how support access is limited, recorded and bound by the same rules that protect custome...
Images, documents and exports are some of the most personal data a customer stores. Here is how our media library keeps every file in the right accoun...