Elegovate Docs

Elegovate Platform

Organizations, multitenant isolation, and shared accounts across products.

Elegovate Platform

Concepts and services shared by Notify, ERP Cloud, and future Elegovate products.

Organizations (tenants)

Each customer operates within an organization (called a "company" in the ERP). Users, projects, and email configuration in Notify — or sales, inventory, and employees in the ERP — are scoped to that organization, with no cross-visibility between different customers.

Multitenant isolation

Elegovate uses database schema isolation: each organization has its own PostgreSQL schema, not just a filter column. That means one customer's data is physically separated from another's at the database level, not only at the application level — an extra layer of protection compared to the more common "shared table with a tenant_id" approach.

User accounts

  • Users authenticate in each product panel with service-specific credentials (Notify and ERP maintain separate accounts today).
  • Roles and permissions are defined per product — for example, organization admin in Notify, or granular per-module permissions in the ERP.
  • Elegovate's support team can access administrative functions to resolve issues, with audited access.

Ecosystem

ProductURL
Websiteelegovate.com
ERP (panel)cloud.elegovate.com
Notify (panel)notify.elegovate.com
Documentationdocs.elegovate.com

FAQ

Can I use the same account for Notify and the ERP? Not yet — each product keeps its own user account and organization. If your company uses both, integration between them happens via API, not a shared session.

Is my organization's data visible to other customers? No. The schema isolation described above guarantees that no other customer's query can reach your data, even in the event of an application-level filtering bug.

On this page