One Login, One Database: Why Our Modules Share Everything

Many organizations run their online presence on a patchwork of tools: a website builder, a separate membership plugin, an email marketing service, a course platform, an event registration tool and a help desk. Each has its own login, its own list of people and its own idea of who a customer is. Keeping them in sync becomes a job of its own.

VoVo takes a different approach. Its modules share one login and one database. Here is why we designed it that way, what it makes possible and what it requires of us.

One person, one record

When modules share a database, a person is the same person everywhere. A member who buys a ticket to an event, enrolls in a course and subscribes to a newsletter is one record with a full history, not three separate entries in three tools that may or may not match.

That simple fact unlocks a lot. Emails can reach members of a specific tier. Event attendees can be welcomed into a community. Support agents can see who they are helping. Reports can describe the whole relationship rather than one tool's slice of it.

One login for the team

Staff and volunteers sign in once and reach every module their role allows. Permissions are managed in one place. When someone leaves an organization, removing their access removes it everywhere, rather than requiring a checklist of separate tools.

Shared services make every module better

Because modules share core services, improvements spread. A better media library helps the website, the blog, the shop and the course builder at once. A stronger payment path protects memberships, event tickets and donations together. Backups cover everything in the account rather than one tool at a time.

Turn on what you need

Sharing a database does not mean every organization uses everything. Modules can be turned on as needed, within what a plan includes. A small church might start with a website and events, then add membership and email later. Because the data is shared, adding a module later does not mean importing lists from scratch; the people are already there.

We describe how features are enabled in three switches before a feature turns on.

What it requires of us

A shared database also asks more of us as engineers. Every module must respect the same rules for keeping each organization's data separate, the same permissions and the same ways of saving content. A careless module could affect others, so shared standards and reviews are essential. We explain those foundations in one database, many customers.

People need special handling too, because one person can belong to more than one organization. Their login is shared across accounts on purpose, while their membership and data in each account stay separate.

Moving in is easier

Organizations moving from a patchwork of tools often bring several lists that partly overlap. Bringing them into one database, with careful matching and preserved source records, is part of what our importers do. Once the move is done, the organization maintains one list instead of several. You can read more about imports in how we rehearse a website migration.

Reports across modules

When everything lives in one place, reporting becomes more useful too. Reports can draw on members, events, orders and other records from the same account, instead of someone exporting and stitching together spreadsheets from several tools. Reports still respect permissions and stay within the account and website they belong to, but they can draw on the whole picture.

Fewer integrations to break

Patchwork setups depend on integrations between tools, and integrations break: an update on one side, an expired connection, a field renamed somewhere. Each broken link means missed sign-ups, duplicate records or lost data. Shared modules remove most of those connections entirely, because there is nothing to sync. The modules already share the same records.

Not a black box

Sharing everything inside one account does not mean trapping data there. Organizations can export their data, and their files live in their own storage. A platform should earn continued use by being useful, not by making leaving difficult.

Frequently asked questions

What is an all-in-one business platform?

It is a platform where tools like a website, membership, email, courses and events share one login and one database instead of being separate services.

Do I have to use every VoVo module?

No. Modules can be turned on as your organization needs them, within what your plan includes.

What happens to my members when I add a new module?

They are already in your account, so a new module can work with them right away instead of importing a separate list.