Brilliance One Settings

Configure the platform. Keep routine changes in the business.

Manage organization defaults, branding, permissions, module behavior, communication services, payment providers, AI preferences, integrations, and shared business configuration from one administrative layer.

Brilliance One Settings helps authorized administrators adapt the Business Operating System to the organization without requiring a code change every time a routine business preference, provider, default, or workflow setting needs to change.

Explore Settings View Configuration Controls
Organization • Modules • Permissions • Providers • Integrations
Brilliance One platform settings configuration and administration

Platform Configuration

Strong defaults. Business-controlled configuration.

Configure shared organization information, module behavior, branding, communication services, financial providers, permissions, AI preferences, integrations, and other supported platform settings from one administrative environment.

Organization

Shared Business Defaults

Maintain common organization information, locations, contact details, preferences, defaults, and other settings used throughout the platform.

Modules

Operational Configuration

Configure supported behavior for individual business modules without forcing every operational area into the same set of defaults.

Administration

Controlled Configuration

Use roles, permissions, security groups, module access, and administrative responsibility to help determine who can change important settings.

Configuration Without Unnecessary Development

Routine business changes should not require a software release.

Organizations change providers, branding, defaults, permissions, locations, integrations, communication settings, financial services, and operating preferences over time.

  • Change organization information
  • Update branding
  • Adjust operational defaults
  • Configure module behavior
  • Change communication providers
  • Manage payment providers
  • Control AI preferences
  • Manage integrations
  • Adjust permissions
  • Extend through APIs when configuration is not enough

Automation Without Administration

Configuration should remove technical dependency without removing control.

Administrators should be able to manage ordinary business settings without involving a developer for every routine change.

More specialized requirements can still move into integrations, APIs, or development when configuration alone is not the right solution.

Organization Settings

Configure the information the whole platform can reuse.

Shared business information can provide consistent defaults to modules and workflows that depend on the same organization-level context.

  • Organization name
  • Business information
  • Default contact information
  • Locations
  • Timezone preferences
  • Date and display preferences
  • Business defaults
  • Organization-wide configuration

Shared Configuration

Store common business information once where practical.

Organization-level configuration can give CRM, Accounting, Communications, Scheduling, CMS, HR, POS, Projects, and other modules the same starting business context.

Specialized modules can then add their own settings only where their workflows require something different.

Module Configuration

Shared platform. Specialized operational behavior.

Each module can require different defaults and operational controls. Brilliance One can keep those settings within the same administrative architecture without forcing unrelated workflows to share identical behavior.

Features

Supported Options

Enable or configure supported options within the modules your organization uses.

Defaults

Operational Starting Points

Define appropriate statuses, behaviors, preferences, selections, or defaults that reduce repetitive configuration for routine users.

Administration

Module-Specific Responsibility

Allow authorized administrators to manage configuration appropriate to the business areas they are responsible for.

Connected Configuration

Configure the same platform across very different business functions.

The shared administrative foundation can support settings across customer-facing, financial, workforce, commerce, content, and specialized operational modules.

CRM

Accounts & Relationships

Configure supported customer, lead, relationship, classification, communication, and administrative defaults.

Communications

Email & Messaging

Manage supported sending providers, domains, identities, credentials, departments, and related communication configuration.

Accounting

Financial Configuration

Maintain appropriate financial defaults, payment configuration, provider settings, and module behavior.

Human Resources

Workforce Defaults

Configure supported workforce behavior, access, organizational structure, employee workflows, and HR-specific settings.

CMS

Digital Experience

Maintain supported website, branding, content, public experience, and related CMS configuration.

Industry Modules

Specialized Workflows

Keep industry-specific settings close to the firearms, drug testing, scheduling, course, POS, or other operational workflows they control.

Branding

Make Brilliance One recognizable as your organization.

Supported brand configuration can help maintain a more consistent identity across internal workspaces, portals, forms, communication, and public-facing experiences.

  • Organization logos
  • Portal branding
  • Business identity
  • Visual preferences
  • Theme options
  • Light and dark experiences where supported
  • Communication branding
  • Public-facing presentation settings

Consistent Identity

The software does not have to feel disconnected from the business using it.

Branding can help customer-facing experiences, employee portals, communication, forms, and supported platform surfaces feel more consistent with the organization behind them.

Administrative Access

Configuration power should follow responsibility.

Settings can change communication, payments, access, integrations, AI behavior, module defaults, and other business-critical functions. Not every user should have authority to modify them.

Roles

Use roles to help define broad user and administrative responsibilities.

Permissions

Control supported settings and administrative actions according to the organization's access model.

Security Groups

Organize users with similar responsibilities into appropriate access groups.

Module Access

Limit configuration access to the modules and operational areas appropriate to each administrator.

Administrative Separation

Separate users performing everyday work from users responsible for higher-impact platform configuration.

Change Visibility

Use available logging and administrative history to support review of important configuration activity.

Communication Configuration

Configure how communication leaves the platform.

Where supported, administrators can manage the providers, identities, domains, and credentials used by Brilliance One Communications and Automations.

  • Email providers
  • SMTP configuration
  • SMS providers
  • MMS providers
  • Sending domains
  • Sending identities
  • Department-specific configuration
  • Provider credentials

Shared Communication Service

Configure the provider once. Reuse communication across the platform.

CRM, Marketing, Automations, Scheduling, Projects, Accounting, HR, and other workflows may all need to communicate.

A shared communication configuration can provide a common delivery foundation instead of requiring each module to create another independent messaging setup.

Payment Configuration

Connect supported payment services to the workflows that need them.

Where payment functionality is enabled, administrators can manage supported gateway, credential, and payment-related configuration used by POS, Accounting, invoices, and other financial workflows.

Providers

Payment Gateways

Configure supported payment-processing providers used by applicable Brilliance One transaction and billing workflows.

Credentials

Protected Configuration

Maintain appropriate payment-provider credentials and connection information through protected administrative workflows.

Defaults

Financial Behavior

Configure supported payment and financial defaults used across appropriate billing and transaction workflows.

AI Configuration

AI should participate under administrative control.

Where AI capabilities are enabled, organizations can configure supported providers, models, credentials, preferences, and workflow behavior according to the way they choose to use AI.

  • AI provider preferences
  • Supported model selection
  • API credentials
  • Business defaults
  • Module-level AI behavior
  • Content preferences
  • Workflow configuration
  • Administrative access

Human-Directed AI

AI capability should not remove human responsibility.

Administrators can determine which supported AI services and workflows they choose to enable.

Users remain responsible for reviewing AI-generated output and determining whether it is appropriate before relying on or publishing it.

Integrations

Manage the systems Brilliance One connects to.

Where supported, administrators can manage external services, APIs, credentials, webhooks, and connected applications used throughout the organization's Brilliance One environment.

APIs

External Services

Configure supported API relationships used by external systems and Brilliance One business workflows.

Events

Webhooks

Configure supported webhook behavior for systems that need to exchange event information with Brilliance One.

Security

Connection Secrets

Maintain appropriate API keys, tokens, credentials, and other connection details through protected administrative configuration.

Integrate Instead of Rebuild

Not every external system needs to be replaced.

Brilliance One's broader platform can reduce software fragmentation, but specialized outside services will still make sense for some organizations and workflows.

  • Communication providers
  • Payment services
  • Calendar services
  • Meeting platforms
  • Industry-specific services
  • External APIs
  • Partner applications
  • Custom integrations

API-First Architecture

Replace software where it helps. Integrate where replacement does not.

Settings provides the administrative layer for supported integrations while Brilliance One's API-first architecture provides room for broader extension.

The goal is a connected operating environment, not replacing useful software merely for the sake of consolidation.

Configuration Scope

Some settings belong everywhere. Others belong to one workflow.

Apply configuration at the appropriate scope so shared business standards remain consistent while specialized modules retain the flexibility their operations require.

Global Settings

Shared Organization Behavior

Use organization-level configuration for supported branding, business information, shared providers, defaults, security behavior, and other settings intended to apply broadly.

Module Settings

Specialized Operational Behavior

Use module-specific configuration when Accounting, Communications, CMS, HR, Scheduling, Marketing, POS, Firearms, or another business area requires different behavior.

User Experience

Administrative flexibility should not create user complexity.

Configuration and permissions can help keep everyday user experiences focused while giving administrators access to the deeper controls they are responsible for managing.

  • Role-aware access
  • Module visibility
  • Administrative depth
  • Operational defaults
  • Brand consistency
  • Focused user workflows
  • Desktop access
  • Tablet and mobile access where supported

Appropriate Complexity

Frontline users do not need every administrative option.

A salesperson, cashier, technician, project employee, or customer-service representative should be able to focus on the work they perform.

Configuration belongs with the people responsible for administering the system.

Configure → Integrate → Extend

Use the simplest level that solves the requirement.

Routine business behavior should use configuration where practical. External dependencies can use supported integrations. Specialized requirements can use APIs or development when necessary.

1

Configure

Use existing platform and module settings for standard business behavior, preferences, providers, branding, and administrative requirements.

2

Integrate

Connect supported external systems when the organization depends on capabilities outside the Brilliance One platform.

3

Extend

Use APIs or development for specialized requirements that go beyond available configuration and supported integrations.

Administrative Governance

Configuration changes can affect the entire operation.

Changes to permissions, communication, payments, security, integrations, AI, modules, and shared defaults can have consequences beyond the Settings screen.

  • Administrative permissions
  • Change review
  • Security configuration
  • Communication credentials
  • Payment settings
  • AI configuration
  • Integration settings
  • Operational defaults
  • Provider management
  • Internal administrative procedures

Change With Intent

Flexible configuration still requires responsible administration.

Organizations should determine who is allowed to change high-impact configuration and establish internal processes for reviewing changes that affect security, financial workflows, integrations, communications, customer experiences, and other critical operations.

Platform Administration

Modern platforms are highly configurable. Brilliance applies configuration across operations.

Modern CRM and customer platforms already provide extensive account, branding, feature, permission, provider, payment, AI, and integration settings. Brilliance One extends the same administrative concept across customer, ERP, workforce, commerce, content, industry, and other operational workflows.

Customer

CRM & Engagement

Configure customers, communications, marketing, automation, websites, and other customer-facing capabilities from the broader shared platform.

Operations

ERP & Workforce

Extend administrative settings into accounting, HR, projects, inventory, scheduling, POS, documents, and other internal business functions.

Specialized

Industry Configuration

Keep specialized settings for firearms, drug testing, courses, and other industry workflows inside the same administrative architecture.

Configuration Standards

Consistent where possible. Flexible where necessary.

Brilliance One Settings is designed to provide administrators with meaningful control while keeping configuration structured and understandable as the platform expands.

Defaults

Practical Starting Points

Begin with platform defaults and adjust supported settings as the organization establishes its own operating standards.

Consistency

Shared Platform Behavior

Use organization-wide settings where multiple modules depend on the same information or expected behavior.

Specialization

Module-Specific Controls

Allow specialized workflows to retain the configuration they need without forcing those settings onto unrelated areas.

Extension

APIs & Integrations

Use supported APIs, integrations, webhooks, and development when ordinary configuration is not enough.

Brilliance One Core

One shared foundation. Used throughout the platform.

Core provides the relationship, communication, automation, identity, security, configuration, and administrative capabilities that support the broader Brilliance One Business Operating System.

CRM & Relationships

Accounts

Manage customers, prospects, leads, organizations, contacts, vendors, suppliers, partners, and relationship history through one connected business record.

Explore Accounts

Locations

Addresses

Maintain billing, shipping, service, customer, employee, vendor, job-site, and operational locations as reusable records connected to the business activity that depends on them.

Explore Addresses

Email, SMS & Messaging

Communications

Connect email, SMS, MMS, campaigns, templates, lists, replies, delivery activity, and communication history with the customers and business records behind every conversation.

Explore Communications

Workflow Automation

Automations

Automate supported email, SMS, tagging, notifications, delays, follow-up, and repeatable processes so people can focus on decisions while software handles routine work.

Explore Automations

Identity & Access

Users

Manage identities, roles, permissions, security groups, profiles, account relationships, module access, authentication, and operational responsibilities across Brilliance One.

Explore Users

Platform Protection

Security

Protect business information with authentication, authorization, roles, permissions, security groups, encryption, session controls, logging, monitoring, and administrative safeguards.

Explore Security

Platform Configuration

Settings

Configure organization defaults, branding, permissions, communication providers, payment services, AI preferences, integrations, module behavior, and shared platform settings.

Explore Settings

Data Operations

Tools

Import, export, map, validate, review, migrate, clean, and maintain supported business information with administrative workflows designed for controlled data operations.

Explore Tools

Brilliance One Settings

Configure the platform. Keep control in the business.

Manage organization defaults, branding, module behavior, permissions, communication providers, payment services, AI preferences, integrations, global settings, and specialized operational configuration from the shared Brilliance One administrative foundation.

Build Your Estimate Discuss Brilliance One

Brilliance One • Settings • Configuration • Administration • Connected Operations