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
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:
- Organizations sign up and become Tenants
- Each tenant has Users who can log in and use the system
- Tenants manage their own tours, drivers, and bookings
- 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​
- Learn about Tenants and how they isolate data
- Understand User roles and permissions
- Explore the API documentation