Note: This article is updated weekly throughout the month as new SafeBase features are released. All updates are also published on our Product Updates site.
Table of Contents
AI Answer Customization and Content Collections
Why it matters
Polished, customer-ready answers out of the box: AI Answer Customization lets teams control tone, verbosity, regional style, and formatting before answers are generated, drastically reducing manual edits.
Consistency at scale: Reusable prompt presets keep responses on-brand and aligned across teams, customers, and regions.
Right content for the right questionnaire: Content Collections give users fine-grained control over which Trust Library content AIQA pulls from on any given run.
Framework- and audience-specific responses: Easily scope AIQA to a compliance framework (SOC 2, HIPAA), a product line, a deployment model, or a customer segment.
Less noise, more relevance: Excluding outdated or internal content from external assessments improves answer quality and trust.
Whats New
AI Answer Customization
Admin-configurable prompt presets controlling tone (Professional / Business Casual / Conversational), verbosity (Brief / Standard / Detailed), language, and regional style.
Additional Styling Instructions (up to 1,000 characters) for fine-tuning — for example, British English, on-premises rules, or product naming conventions.
Knowledge base matching settings, comment controls, and answer auto-approval are now managed inside each preset.
Test AI Answer Style preview lets users validate a preset without consuming AI credits.
Duplicate-and-edit workflow to quickly spin up variants.
Preset selection happens at runtime via the Answering Mode modal.
Content Collections
Admins can curate subsets of Trust Library content — filtered by content type (documents, knowledge base entries, Trust Center items) and tags — and apply them per AIQA run.
Built-in collection testing to verify the right content is returned before applying to a real questionnaire.
Collections also work with Trust Library Search and Ask AI for scoped exploration.
The Questionnaire Details View records which collection was used, giving a clear audit trail.
Edits to a collection apply only to future AIQA runs — past questionnaire results stay intact.
Learn more at AI Answer Customization and Trust Library - Content Collections.
(Early Access) Multi-CRM
Availability Note: This feature is in Early Access. Reach out to your CSM if you’d like it enabled for your account.
This update is designed for larger enterprises that operate across multiple business units, including organizations that have grown through mergers and acquisitions, where a single CRM connection created manual work, reduced visibility into deal data, and added friction to CRM-dependent workflows.
The Solution
As part of Early Access, the following is now supported:
A single SafeBase organization can connect to multiple Salesforce instances.
Rules Engine is supported for each connected Salesforce instance.
Customers can manage access requests and account linking across multiple Salesforce instances in the SafeBase app UI.
Activity sync is supported for multiple Salesforce instances.
The SFDC Query Retool app now supports querying any connected Salesforce instance.
Analytics dashboards (Enterprise Analytics, Won Deals, and Open Deals) now include a CRM Instance(s) filter and a CRM Instance column for each connected Salesforce instance.
Customer Type, Revenue, and Deal Stage fields can be pulled from multiple Salesforce instances for display on the Accounts and Questionnaires pages.
Sync jobs, such as linking SafeBase accounts to SFDC accounts and pulling SFDC deal data for linked accounts, are supported for any connected Salesforce instance.
Additional notes
Customers who want to automate Trust Center access requests across multiple Salesforce instances will still need to use the Rules Engine through Solutions.
Multi-CRM currently supports multiple Salesforce instances only; multiple HubSpot or Dynamics instances are not supported at this time.
This feature is currently available by request for interested Early Access customers.
(Early Access) Account Member Permission Profiles
Availability Note: This feature is in Early Access; reach out to your CSM if you’d like it enabled for your account.
Account Member Permission Profiles extend SafeBase Permission Profiles down to the individual Account Member level, so Trust Center access can be tailored per person—not just per company.
Previously, Permission Profiles were only applied at the Account level, so every contact at the same company saw the same content. During customer audits, it’s common to have a single contact who should see more sensitive documentation than others at their organization.
The Solution (Early Access)
Assign Permission Profiles directly to individual Account Members (in addition to existing Account-level profiles).
Trust Center reviewers see access based on the sum of profiles assigned at the Account and Account Member levels.
Preview the Trust Center exactly as a specific account member would see it.
Configure default expiration timelines for Account Member Permission Profiles.
Expired profiles are soft-deleted and can be re-granted without losing history.
Automate Account Member Permission Profile assignment via the Rules Engine, based on fields in customer CRMs.
Notes
Account Member profiles are additive on top of the Account’s profiles; they don’t replace Account-level permissions.
