Authentication and Environment Access
Customer-specific authentication establishes the authorized environment before access to records and configured Platform capabilities is provided.
Security & Data Architecture
CONTROL • SEPARATION • ACCOUNTABILITY
Shared SaaS Platform. Dedicated Database Per Client.
Cool Life maintains one Business Management Platform while providing each customer a dedicated operational database, customer-specific authentication, permission-based access, and controlled visibility into authorized information and activity.
Permission-based document access within a controlled customer environment
A Clear Customer Data Boundary
One maintained Platform with a dedicated operational database for each customer.
Cool Life provides one maintained Business Management Platform while assigning each customer a dedicated operational database for its records, settings, permissions, workflows, and authorized Platform activity.
Customer operational records are maintained in the database assigned to that customer rather than relying solely on customer identifiers or software filters inside one consolidated operational customer database.
Architecture at a Glance
Shared application capabilities with a dedicated database boundary for each client.
The diagram shows how authentication, divisions, locations, permissions, integrations, and approved access connect to the database assigned to each customer.
Dedicated Database Per Client
Database-level tenant isolation supports control without giving up the benefits of SaaS.
Each client has a dedicated operational database for its records, configurations, permissions, workflows, and related Platform data while continuing to receive centrally maintained application improvements.
The technical description is a multi-tenant SaaS application layer with database-per-tenant data isolation. Customer separation therefore does not depend solely on filtering rows inside one consolidated operational customer database.
How the Model Works
- The shared SaaS application provides maintained Platform capabilities
- Each customer has its own access address and may use a branded address
- Each customer maintains its own user login credentials
- A customer login authorizes access only to its assigned environment
- Role-based permissions govern access within the customer database
- Workflows and integrations remain subject to authorization controls
Customer-Level Access and Control
Each customer controls access within its own database.
Each Cool Life customer has its own access address and user credentials. A customer may also use a branded address such as its own portal domain.
Users receive authorization within the customer environment for which their credentials were established. Organizations then control the records, tools, reports, workflows, documents, and administrative functions available to each user.
Customer-Controlled Security
- User, administrative, read, and write access
- Password and authentication requirements
- Two-factor authentication
- Session and query timeout settings
- Permissions for tables, fields, discovery, queries, and reporting
The Tools
Security Is Applied in Layers
Database separation is one part of the control model. Authentication, authorization, permissions, document controls, activity history, and administrative decisions work together to govern access.
Role-Based Permissions
Administrative controls determine which users can view, add, edit, manage, report on, or share authorized information.
Vault Room Controls
Rooms, folders, user access, document protections, downloads, and activity history help organizations control confidential file exchange.
Activity and Audit Visibility
Authorized activity views and history help administrators review access, actions, document engagement, and workflow progress.
Controlled Integrations
API credentials, permissions, application rules, and customer authorization determine which approved data and actions an integration can use.
Encrypted in Transit and at Rest
Sensitive information is protected while it is being transmitted and while it is stored, helping reduce exposure if data is intercepted or infrastructure is compromised.
Secure Document Control
Keep confidential files out of scattered email threads.
Vault Rooms provide a controlled place to organize and exchange confidential documents for due diligence, financing, audits, legal review, board materials, customer delivery, and other sensitive processes.
Administrators can control access by user, organize files by room and folder, apply available document protections, and review authorized activity throughout the process.
Document activity and access visibility for authorized administrators
Defined Access Boundaries
Defined Boundaries for Access, Integrations, and Secure Views
Connected capabilities do not receive broad access simply because they are available. Each access path remains subject to credentials, permissions, scope, and application rules.
REST API
Approved integrations can connect authorized Cool Life Platform records and actions with other business systems. API access is limited to the information and functions approved for the integration.
Protected Vault Room files, users, permissions, audit history, and document activity are not exposed through the API.
Session and Login Protection
Customer-specific credentials, authentication requirements, and two-factor authentication help control who can enter each customer environment.
Session and query timeout settings help reduce exposure when authorized access is left inactive or unattended.
Secure Views
All CRM data remains private and is not exposed through Secure Views.
Vault Rooms remain accessible only to the people you specifically provide access to, through a controlled view.
Administrative Control
Customer administrators control users, roles, and permissions according to each person’s responsibilities and the organization’s process.
Designed for Technical Review
Clear language for due diligence and security conversations.
Cool Life describes its architecture precisely: a shared SaaS Platform with a dedicated operational database per client.
The application layer is centrally maintained, while the customer database model provides database-level tenant isolation. Database architecture does not replace authentication, authorization, permissions, API controls, integration credentials, or application rules.
Topics We Can Review
- Customer database architecture and tenant boundaries
- User authentication and role-based permissions
- Vault Room access and document controls
- Activity history and administrative visibility
- Integration, API, and optional AI boundaries
- Implementation and customer configuration needs
One Platform. Complete Control.
Security should support the work without making the process harder to manage.
Cool Life brings secure document exchange, customer records, workflows, projects, reporting, marketing, and approved public-facing experiences into one configurable Platform.
Organizations can begin with Vault Rooms or another immediate need, then connect additional capabilities while preserving defined access, permissions, and accountability.
Review Your Security and Data-Control Requirements.
Tell us what information you need to protect, who should have access, and how the work needs to move. We will focus the conversation on the controls, architecture, and capabilities relevant to your organization.
