Skip to main content

Concepts

Understand the fundamental concepts that power Tourfold's multi-tenant architecture and data model.

Core Conceptsโ€‹

Tenantโ€‹

An organization (e.g., Acme Inc.) that owns users, tours, and configurations. Each tenant operates in complete isolation with its own users, data, and settings.

Key Features:

  • Isolated multi-tenant architecture
  • Custom subdomain per tenant
  • Authenticated tenant self-service API (/api/v2/tenant)
  • Own UUID and user base

Userโ€‹

A person with credentials within a Tenant. Users have roles that determine their permissions and capabilities.

User Roles:

  • OWNER: Full permissions for the tenant
  • USER: Standard user with restricted capabilities

Skillsโ€‹

Learn how people and resources provide skills, how work expresses requirements, and which skills Tourfold manages automatically. Includes the availability of planned Tour and Vehicle checks.

Tours, Tasks and Vehiclesโ€‹

Follow the planned standard workflow from planning to completion. A short overview and focused guides explain shared work, Vehicle assignment and location reporting.

Data Modelโ€‹

Tenant Isolationโ€‹

Every tenant operates independently:

  • Separate user bases
  • Isolated data storage
  • Independent configurations
  • Custom branding

User Managementโ€‹

Users belong to a specific tenant and can have different roles:

  • Each user has a unique UUID within their tenant
  • Users can be assigned to tours and cases
  • Role-based access control (RBAC)

Understanding the Architectureโ€‹

Tourfold is designed as a multi-tenant SaaS platform where:

  1. Organizations sign up and become Tenants
  2. Each tenant has Users who can log in and use the system
  3. Tenants manage their own tours, drivers, and bookings
  4. All data is completely isolated between tenants

Use Casesโ€‹

For Platform Administratorsโ€‹

  • Understand how tenant isolation works
  • Manage tenant metadata via public v2 APIs
  • Configure branding and URLs

For Developersโ€‹

  • Implement tenant-aware API clients
  • Handle user authentication
  • Understand role-based permissions

Next Stepsโ€‹