Supporting Several Websites Under One Account

Many organizations eventually run more than one website. A ministry has a main site and a separate site for a conference. A business has a company site and a site for a product. A coach has a personal brand site and a workshop site. Managing them as completely separate accounts means separate logins, separate billing and separate lists of people. Managing them as one undifferentiated pile leads to mistakes.

Our platform supports several websites within one account, each kept clearly separate where it should be and connected where that helps. Here is how.

Each website is its own space

Inside an account, each website has its own:

• Pages, menus, header and footer
• Theme, colors and fonts
• Blog posts, categories and tags
• Forms and their submissions
• Uploaded files in the media library
• Search settings, redirects and sitemap
• Domain bindings

Editing one site never changes another. A page called "About" can exist on both without conflict, because addresses are unique within each website, not across the account.

Records know which site they belong to

Most records carry not just the account they belong to, but the specific website. Our data layer uses that to show only the current site's content in each screen. When an administrator switches between websites, every list, form and setting switches with them.

That second layer of separation follows the same principles as separating accounts, described in one database, many customers.

What is shared on purpose

Some things belong to the account as a whole rather than to one website:

• The team members and their roles
• Billing and the plan
• Some account-wide records, such as members in certain modules

Sharing those makes sense: the same staff manage both sites, and the organization pays once. Where a module's records are account-wide today, imports into a second website are handled carefully so data does not land in the wrong place.

Domains point to the right site

Each website can have its own domain. When a domain is connected and verified, it is bound to a specific website in the account, so visitors to that domain see the right site. Search settings use the site's own preferred address for canonical links and sitemaps, which we explain in custom domains and canonical URLs.

Imports keep sites separate

When an organization brings in content from an existing website, the import is tied to a specific destination website. A second imported site becomes its own website in the account, with its own pages, forms and uploads. Credentials for each source website are stored separately, so connecting one source never replaces or removes another.

Background work remembers the site

Background jobs, such as processing images or sending form notifications, remember which website they belong to as well as which account. That keeps a form submission on one site from triggering a notification configured for another. The pattern is the same one described in background jobs that remember their context.

Caches separate sites too

Cached menus, settings and pages include the website in their keys, so two sites in one account never see each other's cached content. That detail is easy to miss and important to get right.

Switching websites is explicit

Administrators choose which website they are working on with a clear switcher, and the current website is always visible. That small piece of interface prevents a common mistake: editing the wrong site because two look similar. Actions that change content, settings or files apply to the website currently selected, and the platform confirms that the selected website belongs to the account before acting.

One team, many sites

The result is an account where a team can manage several distinct websites with one login, one bill and one set of permissions, while each site keeps its own identity and content. It reflects the broader idea behind our platform: share what should be shared, separate what should be separate and be deliberate about which is which.

Frequently asked questions

Can I run more than one website from one VoVo account?

Yes. An account can contain several websites, each with its own pages, theme, forms, files, settings and domain.

Will editing one website affect another?

No. Pages, menus, themes and settings belong to a specific website, so changes stay within that site.

Are team members shared across websites?

Yes. Team members and their roles belong to the account, so the same people can manage each website their role allows.