Global Settings
Global Settings allow administrators to configure organization-wide settings in Nexus. Changes made here affect the entire platform and help align Nexus with your organization's terminology, processes, reporting structure, and branding.
Important: Global Settings are only accessible to Administrators. Changes take effect immediately across the platform.
📽️Watch a 5 min video on the navigation
Accessing Global Settings- Navigate to Administration.
- Select Global Settings.
Before You Begin
Before configuring Global Settings, identify the stakeholders who can help answer the following questions:
✅ What terminology does your organization use?
✅ How much control should requesters have over visits?
✅ Who should have access to reporting?
✅ How should confidential visits be handled?
✅ What branding assets will be used?
✅ Who should manage Discussion Leaders?
Jump to each section
System Terminology
System Terminology allows you to customize labels throughout Nexus so the platform reflects the language already used within your organization.
________________________
Briefing Program Name
The official name of your briefing or customer engagement program.
Examples
- Executive Briefing Center
- Customer Experience Program
- Executive Engagement Program
Recommendation: Use the name most commonly recognized within your organization.
Briefing Program Name Abbreviation
A shortened version of your program name used in areas where space may be limited.
Examples
- EBC
- CEP
- CEC
Email / Invitation From Name
The sender name displayed on system-generated emails and invitations. This is a global setting.
Examples
- Executive Briefing Center
- Customer Experience Team
- Briefing Operations
Recommendation: Use a sender name that recipients will immediately recognize.
Label for the Team Member Who Manages Visits
Defines the title used for the person responsible for coordinating customer engagements.
Common Examples
- Briefing Manager
- Strategic Engagement Manager
- Program Manager
- Customer Experience Manager
Label for the Internal Team Member Who Requests Visits
Defines the title used for the employee who submits visit requests and typically owns the customer relationship.
Common Examples
- Account Manager
- Host
- Requester
- Account Executive
- Customer Success Manager
Label for Presenters
Defines the title used for speakers and subject matter experts.
Common Examples
- Presenter
- Discussion Leader
- Subject Matter Expert (SME)
- Speaker
Label for Agenda Topics
Defines the term used for individual sessions within a visit agenda.
Common Examples
- Topic
- Session
- Discussion
- Agenda Item
Label for Feedback Form
Defines the label used for post-visit feedback collection.
Common Examples
- Feedback Form
- Survey
- Evaluation
- Customer Feedback Survey
Account Manager Settings
Account Manager Settings determine how requesters interact with visits and scheduling.
Number of Days Before a Confirmed Visit That Account Managers Can Update Visit DetailsDefines how close to the visit date requesters can make changes.
Why it matters: Helps prevent last-minute updates that may disrupt planning and logistics.
Number of Days an Incomplete Visit Can Remain Before Automatic Deletion
Determines how long unfinished visit requests remain in the system.
Why it matters: Keeps the request queue clean and prevents outdated requests from accumulating.
Number of Dates an Account Manager Can Hold
Defines how many potential visit dates a requester can reserve using the Hold Date feature.
Why it matters: Provides scheduling flexibility while preventing excessive calendar holds.
Number of Days a Date Can Be Held Before Deletion
Defines how long a held date remains reserved before being released automatically.
Why it matters: Ensures unused reservations become available to other users.
Allow Account Managers to Hold Dates Without Completing a Request
Allows users to reserve dates before submitting a complete visit request.
Best for: Organizations that frequently schedule dates before gathering all visit details.
Hide Availability Calendar from Account Managers
Controls whether requesters can view scheduling availability.
Enabled: Scheduling is managed more centrally by the briefing team.
Disabled: Requesters can see and use available dates directly.
Reporting Settings
Reporting Settings control access to reporting and determine how fiscal periods are calculated.
Reporting AccessChoose which user roles can view reports.
Available options:
- Briefing Managers
- Administrators
Recommendation: Most organizations give reporting access to both Briefing Managers and Administrators.
Fiscal Start Month
Defines the first month of your organization's fiscal year.
Recommendation: Match your organization's official fiscal calendar.Confidential Visit Settings
Confidential Visit settings allow sensitive engagements to be hidden from general view.
Enable Confidential VisitsAdds a Confidential checkbox to the Visit Information screen.
When selected, the visit can display a confidential label instead of the actual visit name.
Common Use Cases
- Executive meetings
- Strategic customer engagements
- Product roadmap discussions
- Sensitive business reviews
Confidential Visit Label
Defines what users see when viewing a confidential visit.
Common Examples
- Confidential
- Confidential Visit
- Private Meeting
- Restricted Access
Recommendation: Use simple, easily understood language such as "Confidential Visit."
Miscellaneous Settings
Miscellaneous Settings govern attendee management, site types, and CRM opportunity configuration.
Allow Briefing Managers to Update Attendee Email AddressesDetermines whether Briefing Managers can update attendee email information.
Why it matters: Helps maintain accurate attendee communications and reporting.
Allow Account Managers to Update Attendee Email Addresses
Determines whether requesters can update attendee email information.
Why it matters: Allows customer-facing teams to keep attendee information current.
Site Types
Site Types categorize engagement activities.
Available options:
EBC
Executive Briefing Center engagements.
Event
Large-scale customer programs, conferences, or special events.
Reference
Customer reference activities, reference calls, or advocacy engagements.
Recommendation: Enable only the site types that your organization actively uses.
Include Closed Opportunities
Available for organizations integrated with Salesforce, Dynamics, or Oracle.
Allows closed opportunities to be associated with visits for reporting purposes.
Why it matters: Helps measure the relationship between customer engagements and business outcomes.
Closed Opportunity Date Range
Defines which closed opportunities qualify for inclusion.
Closed # Days Before
Determines how many days before a visit an opportunity may have closed and still be associated with the visit.
Closed # Days After
Determines how many days after a visit an opportunity may close and still be associated with the visit.
Recommendation: Align these settings with your organization's sales cycle.
Branding Settings
Branding Settings allow you to personalize the Nexus experience for internal and external users.
External Header ImageThe banner image displayed on public-facing request pages.
Best Practices
- Use a high-quality image.
- Avoid excessive text.
- Choose imagery aligned with your brand.
Company Logo
The logo displayed throughout the platform.
Supported formats:
- PNG
- JPG
Maximum file size:
- 2 MB
Note: The preview updates immediately. The ribbon logo updates after your next login.
Recommendation: Use your current approved corporate logo.
Discussion Leader Settings
Discussion Leader Settings determine who can view and manage Discussion Leader profiles.
Permission LevelsNo Access
Users cannot access Discussion Leader Management.
Read Only
Users can view profiles but cannot make changes.
Edit
Users can view and maintain Discussion Leader information.
Typical Permission Model
| User Role | Recommended Access |
|---|---|
| Caterer | No Access |
| Discussion Leader | Edit |
| Account Manager | Read Only |
| Briefing Manager | Edit |
Important: Administrators and BES Admins always have full Edit access and cannot be restricted.