We have a screen flow that collects a password from the user using a Password field component. That masks the input on screen, but when looking at debug logs, the value of that field gets written to the debug log in plain text. Is there a way to flag that field so it doesn't get written to a debug log?

  • Create/use a managed package for the screen flow? this way the debug log is not visible
    – cropredy
    Sep 10, 2022 at 0:43

1 Answer 1


This is a great use case for implementing a more robust logging framework like NebulaLogger. It comes with OOTB support for metadata-driven masking rules.

  • 3
    While this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference. Furthermore, Nebula or other higher-level logging solutions only solve the masking problem for its own logs. For admins with access to debug logs, there's no way to mask. (SF recently started masking some passwords in debug but that only covers a small % of use cases)
    – identigral
    Sep 8, 2022 at 16:44

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .