Locations
Structured Address Records
Maintain customer, billing, shipping, service, workplace, facility, vendor, and other locations in a structured format that connected workflows can reuse.
Brilliance One Addresses
Store it once. Use the context everywhere it belongs.
Centralize addresses, locations, phone numbers, email addresses, websites, related contacts, important dates, credentials, and supporting relationship data for use across Brilliance One.
Brilliance One Addresses provides structured relationship and location data that can support CRM, accounting, scheduling, projects, HR, communications, documents, service, and other operational workflows without recreating the same information in every module.
Addresses • Locations • Contact Methods • Relationship Data
Shared Relationship Data
More than an address field.
Addresses provides a reusable structure for physical locations, communication points, related people, important dates, credentials, documents, and other information tied to the relationships and operations inside Brilliance One.
Communication
Contact Methods
Keep phone numbers, email addresses, websites, social profiles, alternate contacts, and other communication information connected with the underlying relationship.
Supporting Context
Dates, Credentials & Records
Associate important dates, licensing information, insurance records, credentials, supporting documents, and related entities where those workflows require additional context.
Address & Relationship Capabilities
Structure the details the rest of the business depends on.
Brilliance One can organize more than a single postal address around a relationship, facility, person, or operational record.
Addresses
Physical Locations
Maintain structured street, city, state or region, postal code, country, and related location information.
Phone
Multiple Phone Numbers
Maintain appropriate business, mobile, alternate, emergency, or other phone numbers associated with the relationship.
Email Addresses
Store appropriate email contact points and associate them with the person, organization, or relationship that owns them.
Web
Websites & Digital Profiles
Maintain websites, social profiles, and other supported digital contact or identity information where useful to the relationship.
Related People
Additional Contacts
Associate alternate contacts, emergency contacts, family members, site contacts, managers, or other related people where the business workflow requires them.
Important Dates
Lifecycle Information
Maintain relevant birthdays, anniversaries, expiration dates, renewal dates, policy dates, and other relationship milestones.
Credentials
Licensing & Qualification Records
Associate appropriate licenses, credentials, qualification details, expiration dates, and related supporting records where configured.
Insurance
Coverage Information
Maintain applicable insurance information, supporting documentation, effective dates, and renewal information where required by the workflow.
Documents
Supporting Records
Associate appropriate files and supporting documents with the location, credential, person, organization, or business relationship they document.
Location Types
One relationship can have many places.
A single customer, organization, vendor, employee, or facility may have multiple locations serving different business purposes.
Primary Address Maintain the primary location associated with a person, organization, customer, vendor, or other relationship.
Billing Address Associate financial correspondence and billing location information with accounting and customer workflows.
Shipping Address Maintain locations used for products, deliveries, documents, fulfillment, or other physical activity.
Service Location Track where installation, maintenance, inspection, cleaning, repair, consultation, or other service work occurs.
Business Location Represent offices, branches, retail locations, warehouses, facilities, or other operating sites.
Additional Locations Maintain other relationship-specific locations when one address is not enough to represent the business context.
Operational Locations
The customer address may not be where the work happens.
Businesses that perform work at customer sites need to distinguish the relationship itself from the physical places where services, projects, appointments, deliveries, inspections, or other work occurs.
- Customer headquarters
- Billing location
- Service address
- Project location
- Delivery location
- Facility or branch
- Appointment location
- Operational site
Location Context
A relationship and a location are not always the same thing.
One commercial customer may have a corporate office, billing address, warehouse, and multiple service sites.
Separating those locations while keeping them connected to the same account helps scheduling, projects, accounting, service, documents, and reporting work with the correct place.
Contact Information
Keep communication points with the relationship.
A physical address is only one part of relationship data. People and organizations can have several ways to contact, identify, or reach them depending on the purpose.
- Phone numbers
- Email addresses
- Websites
- Social profiles
- Emergency contacts
- Alternate contacts
- Preferred contact information
- Business-specific communication points
Shared Contact Context
Contact data should not need to be re-entered for every workflow.
When a phone number, email address, website, or location belongs to the underlying relationship, supported Brilliance One workflows can reference that shared information rather than creating unnecessary copies.
This helps keep communication and operational data closer to the record responsible for it.
Structured Data
Consistent enough for systems. Flexible enough for real businesses.
Location and relationship information becomes more useful when it follows a predictable structure that people, modules, APIs, automations, and reporting can understand.
Geographic Data
Structured Locations
Support address lines, city, county, state or region, postal code, country, site information, and international location data within a consistent structure.
Purpose
Location Classification
Identify whether a location is primary, billing, shipping, service, business, workplace, project-related, or another organization-defined type.
Associations
Related Records
Connect locations and contact information with the customer, organization, employee, vendor, project, facility, or other record that gives the data meaning.
Connected Data
One location record. Many business uses.
Shared location and contact data can support multiple Brilliance One modules without requiring every operational area to maintain a completely separate version of the same information.
Accounts
Customers & Relationships
Connect addresses and communication points with customers, leads, organizations, vendors, suppliers, partners, and people.
Accounting
Billing & Financial Context
Reuse appropriate billing, shipping, customer, vendor, and financial location information within supported accounting workflows.
Scheduling
Appointment Locations
Connect appointments, field service, events, customers, resources, and scheduled work with the location where activity occurs.
Projects
Project & Work Sites
Associate projects and operational work with customer sites, facilities, branches, service locations, or other relevant places.
Human Resources
Employee & Workplace Data
Associate appropriate employee, workplace, emergency-contact, and workforce location information with HR workflows.
Communications
Contact Information
Keep phone numbers, email addresses, and other communication points connected with the relationship behind the conversation.
Documents
Supporting Records
Associate documents with addresses, people, credentials, facilities, organizations, projects, or other related business records.
Products & Delivery
Shipping & Fulfillment
Use appropriate location information for product delivery, fulfillment, customer sites, inventory movement, or related physical workflows where supported.
Reporting
Geographic Context
Structured location information can provide geographic context for supported customer, operational, service, financial, or business reporting.
Data Lifecycle
Capture it. Reuse it. Maintain it.
Shared business data remains valuable only when it continues to reflect the real relationship or location behind it.
Capture the Information
Store the appropriate location, communication method, related person, credential, important date, or supporting record with the relationship that owns it.
Reuse the Context
Allow supported modules and workflows to reference the same structured information instead of creating unnecessary duplicate records.
Maintain the Relationship
Update locations, communication points, contacts, dates, credentials, and other shared data as the real-world relationship changes.
Credentials & Supporting Records
Some relationships require more than contact information.
Vendors, employees, contractors, facilities, regulated organizations, and other business relationships may require licensing, insurance, qualification, identification, or other supporting information.
- Licenses
- Insurance records
- Credential information
- Effective dates
- Expiration dates
- Renewal dates
- Supporting documents
- Relationship references
- Permission-aware access
Supporting Context
Keep the credential with the relationship it qualifies.
A vendor's insurance record, an employee credential, or a license tied to an organization is more useful when it remains associated with the record it describes.
Expiration and renewal information can provide additional operational context where those workflows are configured.
Important Dates
Some data matters because of when it changes.
Dates can turn static relationship information into operational information by identifying when something begins, expires, renews, or requires attention.
Credential Expiration
Maintain expiration information for supported licensing, qualification, or credential workflows.
Insurance Renewal
Track applicable coverage dates or renewal information associated with a vendor, organization, employee, or other record.
Relationship Dates
Maintain meaningful dates such as birthdays, anniversaries, start dates, or other organization-defined milestones.
Document Dates
Associate effective, expiration, renewal, or other relevant dates with supporting records where applicable.
Operational Awareness
Use date information as context for supported review, reporting, notification, or workflow processes.
Historical Context
Preserve dates that help explain how a business relationship or supporting record has changed over time.
Data Consistency
Change the relationship. Reduce fragmented copies.
Shared relationship information can reduce the number of independent address and contact records teams must maintain when several workflows depend on the same underlying data.
Fewer Duplicate Records
Reuse appropriate relationship data instead of repeatedly creating separate versions for individual workflows.
Clearer Updates
Keep shared information easier to maintain when a customer, vendor, employee, facility, or location changes.
Better Context
Understand how a location, contact point, credential, or related person connects to the larger business relationship.
Operational Reuse
Use structured information across supported CRM, ERP, communication, scheduling, project, and operational workflows.
Relationship History
Maintain important context around people, organizations, facilities, locations, and supporting records.
Predictable Structure
Consistent fields make relationship and location data easier for users, reporting, APIs, and connected systems to work with.
Connected Systems
Structured data becomes more valuable when systems can use it.
Address and relationship information can support automation, personalization, integrations, documents, APIs, and reporting when the data is stored consistently and associated with the correct business record.
- Communication personalization
- Document generation
- Workflow context
- Scheduling locations
- Billing and shipping information
- Project and service locations
- API integration
- Reporting and segmentation
Reusable Business Data
Data should do more than sit on a profile screen.
The value of a structured address, phone number, email address, service location, or credential increases when other authorized parts of the system can use that information.
Brilliance One is designed so shared relationship data can participate in the larger operating platform where supported.
Relationship Data Security
Shared data does not mean unrestricted data.
Relationship information can include personal, financial, employment, licensing, insurance, contact, or other sensitive records. Brilliance One uses the broader platform security model to help control appropriate access.
- User authentication
- Role-based permissions
- Security groups
- Module-based access
- Administrative controls
- Customer data separation
- Audit-oriented history
- Permission-aware documents
- Security-focused integrations
- Organization-defined access policies
Appropriate Visibility
Reuse information without exposing everything to everyone.
A scheduling user may need a service address without needing access to insurance records. An accountant may need billing information without needing unrelated employee details.
Shared data and controlled access should work together.
Relationship Data Strategy
Modern CRM stores contact data. Brilliance reuses it across operations.
CRM platforms commonly store company addresses, contact information, custom fields, and other relationship details. Brilliance One extends the same principle across a broader CRM + ERP + CMS operating environment.
CRM
Contact & Company Data
Maintain customer, organization, person, location, phone, email, website, and other relationship information.
Operations
Reuse the Same Context
Apply appropriate shared information to accounting, projects, scheduling, HR, documents, service, delivery, and other business workflows.
Platform
Reduce Unnecessary Duplication
Keep important relationship data closer to one connected foundation instead of creating another independent copy for every application.
Included in Brilliance One Core
Shared relationship data belongs in the foundation.
Brilliance One Core provides the users, accounts, permissions, security, settings, communications, automation, and platform infrastructure that allow address and relationship information to support broader business workflows.
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 AccountsLocations
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 AddressesEmail, 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 CommunicationsWorkflow 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 AutomationsIdentity & Access
Users
Manage identities, roles, permissions, security groups, profiles, account relationships, module access, authentication, and operational responsibilities across Brilliance One.
Explore UsersPlatform Protection
Security
Protect business information with authentication, authorization, roles, permissions, security groups, encryption, session controls, logging, monitoring, and administrative safeguards.
Explore SecurityPlatform Configuration
Settings
Configure organization defaults, branding, permissions, communication providers, payment services, AI preferences, integrations, module behavior, and shared platform settings.
Explore SettingsData Operations
Tools
Import, export, map, validate, review, migrate, clean, and maintain supported business information with administrative workflows designed for controlled data operations.
Explore ToolsCore Platform
Relationship data starts with Brilliance One Core.
Addresses participates in the shared Brilliance One foundation rather than functioning as a standalone address-management product. Add business modules as your organization needs broader operational capability.
- Shared relationship foundation
- No per-user platform pricing
- Connected Accounts data
- Shared communication context
- Expandable operational modules
- Founders 400 alternative available
Build Your Platform
Start with shared data. Add the workflows that use it.
Use the Brilliance One pricing estimator to start with Core, add the modules your organization needs, and estimate applicable monthly resource usage.
Brilliance One Addresses
Store the relationship once. Use the context wherever it belongs.
Connect locations, addresses, phone numbers, email addresses, related people, important dates, credentials, documents, and supporting records with the customers, vendors, employees, facilities, projects, and business workflows that depend on them.
Brilliance One • Addresses • Location Data • Connected Operations