Skip to main content

#Security163 utenti parlano di questo argomento

3 risposte
  1. Oggi, alle 17:14

    Hi @Rohit .

     

     

    You can handle this using a

    Validation Rule on Opportunity. The rule can check whether the Opportunity was already Closed Won

    and block further updates for Sales Users, while allowing specific users such as System Administrators to edit it.  

     

    This is generally a better approach than relying only on page layout settings, because the validation rule enforces the restriction when the record is saved.  

     

    Hope this helps! 

0/9000

Restriction Rules  Business Requirement    HR users can access all Employee records.    Managers should only see Employees in their own Location.      

5 risposte
  1. Oggi, alle 11:08

    @Hitesh Sharma  

    Yes. A single Restriction Rule can apply to multiple Managers. You don't need one rule per user. 

    Use a shared attribute such as Location and make the rule apply to the Manager group/role, for example: 

    User.Location__c = Employee.Location__c

      

    Then all 10 Managers can use the same rule, provided each Manager has their own Location value. 

      

    HR users:

    excluded from the restriction, so they can see all Employee records. 

     

    So the design is: 

     

    1 Restriction Rule → 10 Managers → each sees only Employees matching their Location.

     

     

0/9000

UPDATE: I spoke to support, and apparently the list view was for backend purposes and was not supposed to be visible. It was not reflecting any actual scan of the files, and we seem to be fine in that regard. I was told that if I can't see the Malicious Files list in the Files app from the App Launcher directly, then there are no files flagging as malicious. 

 

Good morning! 

 

Yesterday I noticed that Salesforce had rolled out this 'Malicious Files' list view, but it seems to be listing most, if not all, of our files as malicious (for context, they are largely just regular PDFs uploaded by me to attach to opportunities for backup & documentation). Does anyone know what is causing these to be in this list view? Is there a different way to upload files that I should be using?  

 

Thank you for your help. 

 

#Salesforce Admin  #Security

2 risposte
  1. Ieri, 13:05

    Hi Levi, good news first: this is not something you did, and your upload method is fine. Salesforce turned on native File malware scanning (Spring 26, still Beta) on by default, and the Malicious Files list is simply where any file the scanner flags shows up. Flagging is the scanner's call, not how you attach the file, so there is no different upload method that avoids it. 

     

    Why plain PDFs get caught: PDF malware heuristics are very sensitive to embedded active content, JavaScript, form logic, or launch actions, which a lot of system-generated backup PDFs carry even though they are perfectly benign. On a Beta at scale, that produces exactly the false-positive wave you are seeing (even Adobe's own PDFs have been flagged by scanners before). 

     

    What to do: 

    1. Do not worry about the files. Flagging does not delete or block them, they stay fully accessible. The list is a review surface, not a quarantine. 

    2. In Setup, open the Salesforce Files security settings, that is where the malware scanning is controlled if the volume is disruptive. 

    3. Since it is a Beta mass-flagging clean files, log a Salesforce Support case reporting the false positives so it gets tracked and tuned. 

     

    if this helps, please mark it as the Best Answer so it helps the next person, thanks šŸ™‚

0/9000

 

hello , i forgot my password and my security question , is there a way to retrieve the password or change it ? 

 

#Security

2 risposte
  1. 1 set, 16:03

    Hi Salma, 

     

    This community can't reset passwords or security questions directly — that has to go through the proper account recovery channel. Which one applies depends on what kind of account this is: 

     

    1. Trailhead/Trailblazer account: Go to

    https://login.salesforce.com or the Trailhead login page and click "Forgot Your Password?" — it'll email a reset link to the address on file. If you no longer have access to that email either, you'll need to submit a case via Trailhead Help: https://trailhead.salesforce.com/help?support=home

     

     

    2. A company/work Salesforce org: Only your org's Salesforce Administrator can reset your password and security question for you — this can't be self-served or done by Salesforce Support directly, since it's your employer's org, not a personal account. 

     

0/9000

Hey Folks, 

 

We have a couple of contractors that are having issues creating passkeys for the upcoming phishing resistant mfa for privileged users update. Thus far, all the regular employees using company issues devices are having having any problems. For these two, one uses a mac and the other uses a virtual windows machine. Because of this, we believe this may be the problem. Does anyone have any experience creating passkeys with these cases? 

 

#Security  #MFA  #PhishingResistantMFA

2 risposte
  1. 1 set, 13:20

    For anyone with this same question - SF support has stated that virtual machines are exempt from this requirement. We did observe this as I was prompted to create a passkey when logging into the environment but the user with the VM was not prompted when they logged in to the same env.

0/9000

Suppose we have 3 users in the same role hierarchy:

Manager → Team Lead → Executive

The OWD for Opportunity is Private.

Now consider:

  • The Executive owns an Opportunity.
  • The Team Lead has Read access through a Permission Set.
  • The Manager has View All on the Opportunity object.
  • The Executive's Salary field is hidden from the Team Lead using Field-Level Security.
  • The Manager can see all Opportunity records, but should not be able to see the Salary field.

Question:

If the Manager has View All

permission on Opportunity, does that automatically allow the Manager to see every field on the Opportunity record, including the Salary field? 

 

#Security

7 risposte
  1. 1 set, 06:10

    Hi @Pranjal Budhlakoti

     

    Adding On 

    @Hitesh Sharma & @Rohit .

     

    No, View All does not automatically give access to every field on an Opportunity.

    View All is a record-level permission. It allows the Manager to view all Opportunity records, regardless of OWD, sharing rules, role hierarchy, or ownership. 

     

    However, Field-Level Security (FLS) controls whether the Manager can see or edit specific fields. Therefore, if the Salary field is hidden from the Manager through FLS, the Manager will not be able to see that field even though they have View All on Opportunity.

    In this scenario:

    • OWD = Private → controls baseline record access.
    • View All → Manager can view all Opportunity records.
    • FLS → still controls visibility of individual fields.
    • View All does not override FLS.

    So the key point is: Record-level permissions and field-level permissions work independently. 

0/9000

 It just started today, 7/22, that when staff export reports, they are asked for verification code. 

When they enter the code from the authentication app, it doesn't work and just keep looping. 

I tried to generate temporary verification code via staff's user account. An email was sent to them but no code and no link, nothing. I don't have the code either. so dead-end. 

 

We use MS SSO for staff to get in Salesforce. Our IT people just enabled passkey method on the network. One staff set up passkey successfully and she could now export reports fine. However, two other staff can't set up passkey, the same, got stuck on verification code screen. 

 

I don't know what else to do. Please advise. 

9 risposte
  1. 31 ago, 17:33

    @Max Wilson I don't think so.  Are you the Salesforce Sys Admin or are you a user and trying to get info for the admin?  I'm happy to help if you can tell me more.

0/9000

Hi All, 

 

Have any of you had any reports of the SF Authenticator app sending approval prompts even when a User is not trying to log in? 

 

I have now had two reports of this behaviour and I am unsure what to do. The login and session mgmt logs are not telling me anything. 

 

Is it enough to have them uninstall/reinstall the app and disconnect on their User record? 

 

Any insight would be helpful! Thanks!! 

 

#Security  #TrailblazerCommunity  #Salesforce Admin  #Salesforce

2 risposte
  1. 31 ago, 13:59

    Hi Eric, Thanks for the thought. I have already done so and there is nothing suspicious.

    Carolyn

0/9000

Hi everyone, 

I'm experiencing an issue in a Salesforce Sandbox when trying to access: 

Setup → App Manager → View App → Manage Consumer Details 

 

When I click Manage Consumer Details, Salesforce opens the Verify Your Identity dialog, but the authentication immediately fails with the following error: 

There are no built-in authenticators available to this browser. 

Verify Your Identity fails with 'There are no built-in authenticators available to this browser' when opening Manage Consumer Details

 

Environment:

  • Salesforce Sandbox
  • Google Chrome

 

What I've already verified:

  • Touch ID is correctly registered as my authentication method.
  • Touch ID works correctly for other authentication requests.

 

From what I've investigated, it appears that the Verify Your Identity dialog may be rendered inside an internal iframe, and the browser is therefore unable to access the registered authenticator. 

 

Has anyone encountered this issue before? Is this a known Salesforce or Chrome limitation, or is there a configuration or workaround that resolves it? 

 

Any help or suggestions would be greatly appreciated. 

 

Thank you! 

 

 

 

#Security

11 risposte
  1. 31 ago, 07:08

    Thanks for sharing this! The high-assurance login setting and removing -test from the URL are useful workarounds to keep in mind. 

0/9000
Sans Gudadhe ha fatto una domanda in #Salesforce Admin

Hi everyone,

I’m facing an issue with Account record visibility in a Salesforce Developer Sandbox and would appreciate some guidance.

  • Account OWD is set to Private.
  • I have refreshed the Developer Sandbox from Production.
  • I manually loaded Account records into the Sandbox.
  • The Account records are owned by me.
  • I and the other users have the Company CEO role.
  • My Account object Read permission is enabled.
  • I can see the Account records in the Sandbox, but the other Company CEO users cannot.
  • In Production, these same users can see Account records owned by me.
  • There are no Account Sharing Rules configured in the Sandbox.

What could be causing the difference in record visibility between Production and the Developer Sandbox? Is there any additional sharing/access setting I should check?

Thanks in advance! 

 

#Salesforce Admin  #Security  #Sandbox  #Salesforce

5 risposte
  1. 27 ago, 06:13

    Hi, Make sure they have a permission of View All on the Account object. It is also good to validate AccountShare object as suggested by Steven, there is a possibility that apex/manual sharing is triggered while loading the records.

0/9000