Brilliance One Settings

Configure the platform. Make it fit the business.

Manage organization preferences, branding, defaults, module behavior, permissions, gateways, integrations, AI preferences, and shared system configuration from one administrative layer.

Brilliance One Settings gives authorized administrators practical controls over how the platform looks, behaves, connects, and supports day-to-day operations without requiring a development change for every routine adjustment.

Organization Branding Permissions Gateways Integrations
Brilliance One administrative settings

Platform Configuration

Control how your Brilliance One environment behaves.

Configure organization-wide defaults, module preferences, visual identity, access behavior, communication services, integrations, and other operational settings from one shared administrative environment.

Configuration

Business-Specific Defaults

Adjust supported defaults, features, workflows, module options, and administrative behavior to better match how the organization operates.

Branding

Visual Identity

Manage supported logos, brand information, visual preferences, themes, and other presentation settings used throughout the platform.

Access

Role-Aware Configuration

Use roles, permissions, module access, and administrative responsibilities to determine which users can view or change appropriate settings.

Organization Settings

Start with the organization itself.

Maintain shared business information and defaults used throughout the Brilliance One environment.

  • Organization name
  • Business information
  • Default contact information
  • Primary locations
  • Timezone preferences
  • Date and display preferences
  • Default business behavior
  • Organization-wide configuration

Shared Defaults

Configure common behavior once where appropriate.

Shared organization settings can provide a consistent starting point for modules and workflows that depend on the same business information.

Module Configuration

Configure the capabilities your organization actually uses.

Module settings can control supported defaults and behavior for different areas of the platform without changing the underlying application code.

Features

Supported Options

Enable or configure supported features and behaviors within appropriate Brilliance One modules.

Defaults

Module Behavior

Define supported defaults that help users start with the appropriate status, workflow, display, or administrative behavior.

Administration

Module-Specific Controls

Give authorized administrators access to configuration appropriate to the modules they manage.

Branding

Make the environment recognizable as your organization.

Manage supported visual and identity settings used across internal workspaces, portals, forms, communications, and other branded experiences.

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

Visual Identity

The software can reflect the organization using it.

Supported branding settings can help maintain a more consistent identity across internal and customer-facing Brilliance One experiences.

Administrative Access

Not every user should control every setting.

Configuration access should reflect each person's role and responsibilities within the organization.

Roles

Use role assignments to help define broad administrative responsibilities.

Permissions

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

Security Groups

Use group-based access where appropriate to organize similar responsibilities.

Module Access

Limit access to settings associated with specific modules or operational areas.

Administrative Roles

Separate routine operational users from users responsible for platform configuration.

Change Visibility

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

Communication Services

Configure how messages leave the platform.

Where supported, administrators can manage communication providers, sending identities, domains, and other delivery settings used by Brilliance One Communications and Automations.

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

Delivery Configuration

Communication infrastructure can be configured around the business.

Different departments, brands, workflows, or operational needs may require different supported sending services or identities.

Payment Configuration

Connect supported financial services.

Where payment capabilities are enabled, administrators can manage supported gateway and payment-related configuration used by financial workflows.

Providers

Payment Gateways

Configure supported payment-processing services used by Accounting, POS, invoices, or other applicable workflows.

Credentials

Protected Configuration

Maintain appropriate payment-service credentials and configuration through protected administrative workflows.

Behavior

Financial Defaults

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

AI Preferences

Configure how AI participates in the platform.

Where AI functionality is enabled, administrators can manage supported provider, model, preference, credential, and workflow configuration.

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

Human-Directed AI

AI configuration should remain under administrative control.

Organizations can determine which supported AI services and workflows they choose to enable, while users remain responsible for reviewing AI-generated output before relying on it.

Integrations

Manage the systems Brilliance One connects to.

Configure supported external services, APIs, credentials, webhooks, and connected applications used by the organization's Brilliance One environment.

APIs

External Services

Manage supported API connections used by external services and Brilliance One workflows.

Webhooks

Event Connections

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

Credentials

Connection Secrets

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

Configuration Scope

Some settings belong everywhere. Others belong to one workflow.

Configuration can be applied at the appropriate level so organization-wide standards remain consistent while modules retain the flexibility needed for specialized workflows.

Global Settings

Shared Organization Behavior

Use global configuration for supported defaults, branding, organization information, shared providers, and behavior intended to apply broadly across the platform.

Module Settings

Specialized Operational Behavior

Use module-specific settings when Accounting, Communications, CMS, HR, Scheduling, Marketing, or another operational area requires its own configuration.

User Experience

Configuration should support the people using the system.

Supported settings can help simplify the experience for routine users while retaining deeper administrative capability for users responsible for managing the platform.

  • Role-aware access
  • Module visibility
  • Administrative depth
  • Operational defaults
  • Brand consistency
  • Responsive experiences
  • Desktop workflows
  • Mobile and tablet access where supported

Appropriate Complexity

Frontline users do not need every administrative control.

Access and configuration can help keep routine workflows focused while preserving the settings and administrative tools leadership or platform administrators require.

Advanced Configuration

Configuration first. Extension when needed.

Routine business behavior should use configuration where practical, while APIs, integrations, webhooks, and development extensions can support more specialized requirements.

1

Configure

Use existing administrative settings and module options for standard business requirements.

2

Integrate

Connect supported external systems and services where the workflow depends on outside capabilities.

3

Extend

Use development or API-based extensions for specialized requirements that go beyond available configuration.

Configuration Standards

Strong defaults. Controlled customization.

Brilliance One Settings is designed to reduce unnecessary technical dependency while still giving administrators the flexibility to refine system behavior as requirements change.

Defaults

Practical Starting Configuration

Begin with platform defaults and adjust supported configuration as the organization establishes its own workflows.

Consistency

Shared Platform Behavior

Use organization-wide configuration where appropriate to help maintain consistency across modules, providers, workflows, and brand settings.

Experience

Responsive Administration

Manage supported configuration through experiences designed to remain usable across modern desktop, tablet, and mobile interfaces.

Extension

APIs & Integrations

Use supported APIs, integrations, webhooks, and custom workflows when configuration alone is not enough.

Administrative Governance

Configuration changes can affect the entire business.

Organizations should control who can change system configuration and establish internal processes for reviewing settings that affect security, communications, financial workflows, integrations, AI, and other critical operations.

  • Administrative permissions
  • Change review
  • Security configuration
  • Provider credentials
  • Payment settings
  • AI configuration
  • Integration settings
  • Operational defaults

Change With Intent

Flexible configuration still needs responsible administration.

Brilliance One provides administrative controls, but organizations remain responsible for determining who can modify them and how configuration changes should be reviewed.

Brilliance One Core

Settings are part of the Core foundation.

Brilliance One Core provides the shared organization, user, permission, security, communication, automation, and platform infrastructure that Settings configures across the broader environment.

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

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

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

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

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

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

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

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

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 Settings

Configure the platform. Keep control in the business.

Manage organization defaults, branding, module behavior, permissions, communication providers, payment gateways, AI preferences, integrations, and other shared configuration from one administrative foundation.

Brilliance One • Settings • Configuration • Administration • Connected Operations

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.

The session has been paused.