Examkin

Question

Difficulty: MediumContent Management and Salesforce Files

A Salesforce Administrator is configuring file governance and sharing controls across several business units. Match each organizational file requirement to the appropriate Salesforce Content and Files capability or setting.

  • Restrict a confidential attachment on an Opportunity record so that only the file owner and explicitly shared users can view it, even if other users have access to the Opportunity record.Set the 'File Privacy on Record' option to 'Private on Record' on the file detail page.
  • Share a product datasheet with an external, unauthenticated client via a web URL that automatically revokes access after 14 days.Generate a Public Link or Content Delivery with an explicit expiration date configured.
  • Grant a group of sales operations users the ability to publish new file versions and edit document details in a shared library without letting them add or remove library members.Assign the 'Author' Library Role to the group within the target Content Library.
  • Prevent all users from generating external encrypted web links for a specific sensitive legal contract stored in Salesforce Files.Toggle the 'Prevent sharing via public link' setting on the individual file detail record.

Answer

Each business requirement is matched to its corresponding Salesforce File feature: 1) Hiding record files from general record viewers corresponds to setting 'File Privacy on Record' to 'Private on Record'. 2) Temporary external URL sharing corresponds to generating a Public Link or Content Delivery with an expiration date. 3) Content publishing without administrative access corresponds to assigning the 'Author' Library Role. 4) Blocking public link creation for a specific file corresponds to enabling 'Prevent sharing via public link' on the file record.
Each requirement leverages a distinct Salesforce Content and Files capability: 'Private on Record' restricts record attachment visibility to file owners/collaborators; Public Links with expiration dates facilitate time-limited unauthenticated external sharing; the 'Author' library role enables version management without library administration privileges; and 'Prevent sharing via public link' disables external URL generation for specific sensitive files.

Step-by-Step Solution

1
Analyze record-level file visibility options in Salesforce Files.
By default, files attached to records inherit the record's access, but changing 'File Privacy on Record' to 'Private on Record' overrides this inheritance for non-owners.
This satisfies the requirement of securing sensitive Opportunity attachments.
2
Evaluate external file distribution mechanisms.
Public Links and Content Deliveries provide unauthenticated URL access with built-in time-based expiration policies.
This fulfills the requirement to share product datasheets externally for 14 days without requiring user logins.
3
Distinguish between standard Salesforce Content Library roles.
The 'Author' role grants document upload and version management permissions without user management privileges, whereas 'Library Administrator' controls member access.
This matches the operational requirement for the sales operations team.
4
Determine file-level public link restriction controls.
Administrators or file owners can toggle 'Prevent sharing via public link' on specific file records to block link generation.
This satisfies the requirement to lock down sensitive legal contracts.

Key Concept

Salesforce Files Security, Library Permissions, and Sharing Controls
Rate this question

Topics

Content Management and Salesforce Files

More questions from this topic