Brilliance One Security

Security belongs at the foundation.

Protect business and customer data with authentication, permissions, encryption, audit visibility, session controls, monitoring, and tenant-specific data architecture.

Brilliance One Security provides shared controls that can extend across CRM, ERP, CMS, communications, documents, financial workflows, employee records, and other connected modules.

Explore Security View Security Controls

Authentication • Permissions • Encryption • Logging • Monitoring

Security Architecture

Protect the platform from the shared foundation.

Brilliance One combines data separation, encryption, credential protection, permissions, logging, session controls, and monitoring to support a layered approach to protecting business information.

Data Protection

Encryption Controls

Sensitive information can be protected using supported encryption controls across appropriate business areas and stored records.

Credentials

Password Protection

Brilliance One uses modern password-hashing controls to help protect stored credentials against common offline attack techniques.

Deployment

Flexible Infrastructure

Support cloud-hosted environments and, where required and supported, deployment models that provide organizations with greater infrastructure control.

Data Separation

Keep tenant data separated at the database layer.

Brilliance One can use a dedicated customer database architecture to provide stronger separation between tenant data than a shared-database model.

Dedicated customer databases
Tenant-specific data separation
Controlled application access
Role-based permissions
Customer-specific configuration
Operational logging
Module-level security
Infrastructure monitoring

Database Architecture

Separation reduces shared-database exposure.

A dedicated database architecture can help reduce certain cross-tenant risks, while application security, configuration, infrastructure, credentials, and operational controls remain important parts of the overall security model.

Authentication

Verify who is requesting access.

Authentication controls help establish user identity before access decisions are applied to protected business data and functionality.

Credentials

Password Security

Use modern credential-hashing practices to help protect stored password material.

Multi-Factor

Additional Verification

Where enabled, multi-factor authentication can add another verification step beyond the primary credential.

Protection

Login Controls

Supported lockout, rate-limiting, session, and account-security controls can help reduce exposure to repeated unauthorized access attempts.

Authorization

Authentication answers who. Permissions answer what.

Brilliance One can use roles, security groups, module permissions, and other access rules to limit what authenticated users can view and change.

Roles
Permissions
Security groups
Module access
Record access
Administrative privileges
Sensitive actions
Business responsibilities

Least Necessary Access

Users should only have access appropriate to their responsibilities.

Permission-aware design helps organizations separate administrative, operational, financial, HR, customer, and other responsibilities throughout the platform.

Encryption

Protect sensitive information where stronger controls are required.

Encryption can be applied to appropriate records and workflows to help protect sensitive data while it is stored and transmitted.

Stored Data

Sensitive Records

Use supported encryption for appropriate sensitive values and protected records stored within the platform.

Transport

Protected Connections

Use encrypted transport for supported web and service communications between users, applications, and platform endpoints.

Secrets

Sensitive Configuration

Protect appropriate API keys, credentials, tokens, and other sensitive configuration data through dedicated security workflows.

Session Security

Protect access after login.

Security does not stop once credentials are accepted. Session handling helps maintain confidence that ongoing requests still belong to an authorized user and valid session.

Session validation
Token validation
Automatic timeouts
Contextual checks
Session expiration
Authentication state
Protected endpoints
Access-policy enforcement

Session Controls

A valid login should not imply permanent access.

Session expiration, token validation, and other supported controls can help reduce the risk created by abandoned, shared, or compromised workstations.

Monitoring

Security also requires visibility into suspicious activity.

Monitoring can help identify failed access attempts, unusual behavior, and other events that may warrant administrative review or defensive action.

Failed Access Attempts

Track supported login failures and repeated access attempts that may require review.

Unusual Activity

Use available security signals to identify behavior that differs from expected application usage.

Rate Limiting

Apply supported request controls to reduce abuse against authentication and application endpoints.

Account Protection

Use supported account-security workflows when suspicious access patterns are detected.

Administrative Review

Give authorized administrators visibility into appropriate security and access activity.

Operational Response

Use logged activity as context when investigating security or access concerns.

Audit Visibility

Know what changed and who changed it.

Operational and security logs can provide a historical record of important access and configuration activity throughout the platform.

Login activity
Configuration changes
Permission changes
Security events
Administrative activity
Module activity
Sensitive actions
Recorded timestamps

Accountability

Important actions should leave a history.

Audit records can help organizations investigate changes, understand access activity, review administrative actions, and support internal governance processes.

Deployment Options

Infrastructure requirements can vary by organization.

Brilliance One can support deployment models appropriate to organizations with different infrastructure, operational, privacy, and control requirements.

Hosted

Managed Cloud Environment

Use a managed Brilliance One environment with platform infrastructure and operational services maintained as part of the deployment.

Dedicated

Customer-Specific Resources

Use dedicated data resources and other customer-specific infrastructure options where the deployment requires additional separation.

On-Premise

Controlled Infrastructure

Where supported, organizations with specific infrastructure requirements can evaluate deployment models that keep more platform resources within their controlled environment.

Security Controls

Layered controls across identity, access, sessions, and activity.

Brilliance One combines multiple security mechanisms rather than relying on a single control to protect the platform.

Monitoring

Suspicious Activity Visibility

Use supported monitoring to identify failed access attempts and other unusual behavior that may require investigation.

Logging

Audit History

Record supported login, configuration, permission, security, and other sensitive administrative activity for later review.

Sessions

Session Integrity

Use supported session handling, validation, expiration, and contextual checks to help reduce unauthorized ongoing access.

Permissions

Role-Based Access

Limit supported modules, records, actions, and administrative functions according to each user's assigned responsibilities.

Shared Responsibility

Platform security also depends on configuration and use.

Security controls can reduce risk, but no software platform eliminates it. Organizations remain responsible for user access, permissions, endpoint security, policies, credential practices, integrations, retention, and other operational decisions.

User access reviews
Strong credential practices
Permission management
Device security
Integration security
Administrative policies
Data retention decisions
Incident-response procedures

Security Is a Process

Good controls still require good administration.

Brilliance One provides security capabilities, but organizations should configure those controls appropriately and maintain their own policies, procedures, training, and operational safeguards.

Brilliance One Core

Security is part of the Core foundation.

Brilliance One Core provides the shared authentication, permissions, session, logging, configuration, and security infrastructure used throughout the broader platform.

Core Workspace

Workspace modules. The shared foundation of Brilliance One.

Manage the core relationship, communication, automation, security, administration, and user capabilities that support the rest of your Brilliance One workspace.

Accounts

Centralize customers, leads, vendors, partners, organizations, and contacts in one connected relationship record with communication history, activity, documents, tasks, financial context, and operational workflows.

Learn about Accounts

Automations

Build repeatable workflows that handle routine follow-up, trigger communications, apply actions, and move work forward based on defined business events and timing.

Learn about Automations

Addresses

Store and organize physical locations for customers, vendors, facilities, offices, service locations, and other business relationships so address data stays connected to the records and workflows that use it.

Learn about Addresses

Communications

Manage email, SMS, MMS, replies, templates, campaigns, delivery activity, and communication history while keeping conversations connected to the customers, contacts, and workflows behind them.

Learn about Communications

Security

Protect business and customer data with authentication, role-based permissions, security groups, controlled access, audit visibility, privacy-oriented controls, and security practices that extend across the Brilliance One platform.

Learn about Security

Settings

Configure organization-wide preferences, branding, defaults, system behavior, connected services, and other administrative options that shape how Brilliance One works across your business.

Learn about Settings

Tools

Access practical utilities for imports, exports, validation, data management, operational cleanup, and other administrative workflows that help teams maintain accurate information and work more efficiently.

Learn about Tools

Users

Manage user identities, roles, permissions, security access, and workspace responsibilities so each person can access the Brilliance One capabilities and information appropriate to their role.

Learn about Users

Brilliance One Security

Protect access. Preserve control.

Use dedicated data architecture, authentication, permissions, encryption, session controls, monitoring, and audit visibility as shared security foundations across Brilliance One.

Discuss Security Visit the Trust Center

Brilliance One • Security • Access Control • Encryption • Audit Visibility