Masset + Salesforce: a door into the home from where your team already works.
Search your synced Salesforce records without leaving Masset, and every share stays tied to the record it belongs to. Engagement writes back automatically, and every search still honors Salesforce's own sharing rules.
Masset Search
Masset_Engagement__c
Retail ROI Calculatorshared to this Opportunity · 40 min ago
Everything your team needs from your content library, without leaving Salesforce.
Masset connects to the records your reps already work in, and never overrides the record-level access Salesforce already enforces.
Search synced Salesforce records right in Masset
When building a share or a Board, search your synced Accounts, Contacts, and Opportunities without leaving Masset.
Every search respects Salesforce's own sharing rules
Masset filters results through Salesforce's UserRecordAccess model, so a rep only sees the records they could already see directly in Salesforce.
Shares stay tied to the right record
Associate a Masset share or content room with the Salesforce record it belongs to, so engagement stays connected to the deal it came from.
Engagement writes back automatically
Every open, share, or download becomes a Masset_Engagement__c record or a standard Task, whichever your team chose during setup. Nobody has to log it by hand.
How the connection works
A managed package, a dedicated user, and you're connected.
Getting Salesforce connected is one small piece of onboarding to Masset, and full onboarding to the platform is measured in hours, not months.
Install the managed package
A Salesforce System Administrator installs the Masset package for admins only, which adds the Masset_Engagement__c object and the two Masset permission sets.
Assign a dedicated Integration User
A Salesforce user built for this purpose, not a named employee, gets the Masset Integration User permission set and owns the OAuth connection, so writeback keeps working when people change roles or leave.
Link the rest of your team
Every other user who needs identity linking gets the Masset Salesforce App User permission set, then a Masset Admin matches Salesforce and Masset users by email or maps them manually.
Engagement tied to the deal, without asking anyone to log it.
When writeback is on, every open, share, or download becomes a Masset_Engagement__c record or a Task on the associated Salesforce record, whichever your team chose. Sales leaders can see which content was in play before a deal closed, without leaving Salesforce or asking a rep to log it by hand.
See the same content and engagement story from the other side of the CRM stack on the HubSpot integration page.
Salesforce gets more reach. It never gets less security.
Every rule that governs Masset applies the same way inside Salesforce. Nothing here is a special case.
Salesforce sharing rules apply first
Every search Masset runs on synced Salesforce records is filtered through Salesforce's own UserRecordAccess model. A rep only sees what they could already see directly in Salesforce.
Only Id and Name ever sync
Whichever Salesforce objects your admin enables, Masset reads only the Id and Name field on each record. Nothing else comes across.
Downloads always route through Masset
Raw asset files are never uploaded to Salesforce. Only engagement metadata (event type, timestamp, and the associated record) writes back.
A dedicated Integration User, not a named employee
The connection is owned by a Salesforce user built for this purpose, so engagement writeback keeps working even when people change roles or leave the company.
Common Questions
Does the Salesforce integration work with Lightning and Classic?
Yes. Masset's Salesforce integration is compatible with both Salesforce Classic and Lightning Experience.
What does Salesforce actually send to Masset?
Only the Id and Name field for every synced object your admin enables (typically Account, Contact, and Opportunity), plus Id, Email, First Name, Last Name, and Is Active for the Salesforce User object used for linking. Nothing else.
Where does engagement data get written back?
Either Masset_Engagement__c, a dedicated custom object added by the managed package, or standard Salesforce Tasks, whichever your admin chose during setup.
Who should be the dedicated Integration User?
A Salesforce user built for this purpose, not a named employee's personal login. That way the connection survives role changes and departures instead of breaking when someone leaves.
See Masset running in your own Salesforce.
Masset starts at $500/mo, unlimited seats. Watch a demo and we'll show you Salesforce, HubSpot, or whatever your team already uses.