Skip to main content
답변 4개
  1. 2023년 6월 18일 오후 12:03

    @Dhanush Hegde Hello, consider trying these options below: 

     

    1. "Page-Level Read-Only Logic:
      • Within your VF page's controller or extension, implement logic that disables or hides any input fields or buttons that allow data modification.
      • This approach ensures that the user can view the page content but cannot make any changes.
    2. Field-Level Read-Only Logic:
      • Use the "rendered" attribute on input fields to conditionally render them as read-only based on the user's profile or specific criteria.
      • For example, you can check the user's profile and only render fields as editable for users with specific profiles, while rendering them as read-only for others.
    3. Profile and Permission Set Settings:
      • Modify the user's profile or assign a specific permission set that restricts their ability to edit records or access certain objects.
      • By removing or limiting the user's edit access at the profile or permission set level, you can ensure read-only access to VF pages and other related objects.
    4. Sharing and Field-Level Security:
      • Adjust the object's sharing settings and field-level security to control the user's access.
      • By setting the appropriate permissions, you can restrict the user's ability to modify records and enforce read-only access.

    It's important to note that while these approaches can help enforce read-only access, it's still crucial to secure your data at the object and record level using Salesforce's built-in security features, such as profiles, permission sets, sharing rules, and field-level security settings."

0/9000