

T4S is an enterprise Salesforce solution designed to streamline file and record transactions with OpenText Content Manager (Previously called TRIM). It simplifies document management, giving you full control over your data flow within Salesforce. With T4S, you'll establish a single source of truth, optimizing efficiency and accuracy in document handling.
Trim Connector (T4S) integrates Salesforce with OpenText Content Manager (TRIM).
Content Manager (formerly HP TRIM/Micro Focus Content Manager) versions 8 and above, and all Salesforce editions. T4S is designed to support real-time, bidirectional document and metadata sync via TRIM Web Services.
Yes, T4S is built with information governance in mind, supporting regulated environments, retention policies, audit trails, and data residency requirements by integrating smoothly with TRIM governance controls.
FuseIT is ISO 27001 certified, and T4S undergoes periodic security testing by external security consultants to ensure the platform meets industry best practices for data protection and security standards.
T4S connects Salesforce (hosted at your regional data center) with Content Manager (either your own on-premise file servers or cloud instance). These two endpoints utilise your already existing environment. T4S introduces no other data location or handling requirement. All files remain stored onshore with no offshore data storage.
Yes, T4S is currently used by multiple Australian state government agencies. FuseIT is also registered with Australian state government panels for procurement, making it easier for government organizations to acquire and implement T4S through established procurement frameworks.
Our experience working with government clients means we understand the unique compliance, security, and operational requirements of the public sector.
T4S is licensed with an annual charge per user. There is an additional annual maintenance subscription for updates and support.
To install and run T4S, you'll need the following components:
Detailed steps are available in the T4S Server Configuration guide, and our team is available to provide assistance.
After we've assisted with your T4S installation, we will guide you through the process to configure mapping so the records and documents from your CRM can be stored in the correct place in OpenText Content Manager.
Once the mapping exercise is complete, an initial data migration and reconciliation process will be run to ensure records in each system are present and accurate. This is also a good time to archive documents from Salesforce so that you are not paying for storage you no longer need.
T4S employs multiple layers of security to protect data transmitted between Salesforce and Content Manager:
These security measures work together to ensure your data remains protected throughout the entire integration process while maintaining seamless functionality between both platforms.
T4S is designed to operate alongside your existing processes and systems. The platform provides:
This flexibility ensures T4S complements your existing workflows rather than requiring you to change how your organization operates. Most implementations can be configured to work with your processes out of the box, with custom integrations only needed for more complex scenarios.
Once T4S is installed, a new user interface control is made available that can be dragged and dropped directly onto Salesforce screen layouts.
You and your team can view relevant documents, upload new files, search Content Manager, and perform other document management operations right where you're already working. Files can be related to Cases, Accounts, Contacts, or any other type of record. This provides a seamless experience that keeps users productive within their familiar Salesforce environment.
Having everything accessible natively within Salesforce means no switching between applications, and no separate logins.
Yes. A single T4S deployment can connect to multiple Salesforce Orgs and multiple Content Manager servers.
This may be used when many non-production environments are sharing the same infrastructure.
Yes. Metadata from Salesforce can be included with containers and documents sent to Content Manager.
Yes. T4S supports bulk file revisions and container creation, with performance exceeding 12,000 containers/hour.
Yes. T4S supports secure Windows authentication.
T4S respects Salesforce profiles and permission sets, and Content Manager access controls. Users can only view/upload documents they are authorized to access in both systems.
Yes. Field mapping is configurable to suit your object structure, label conventions, retention requirements, and metadata policies.
Yes, with the majority of the Headless and oAuth 2.0 Flows, except for the Server-to-Server flows where a UserInfo Session has not been made available by Salesforce.
e.g “OAuth 2.0 JWT Bearer Flow” and “OAuth 2.0 Device Flow”T4S will check the current user’s “UserInfo” and Session to determine if the user has provided their own personal Content Manager credentials to be used by T4S. And if no personal credentials are stored, T4S will use the default Content Manager Integration User.
For documentation and requesting assistance head over to our support centre and we will help you out.

By clicking 'Accept all', you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.