Can an owner stop SyncNow hiding values in a file that holds no secrets?

Yes, one file at a time.

Since version 13.2.49.84 the project owner or a manager can exclude one exact file from SyncNow's secret detector, with a reason, for example a data file whose words password or key are only labels. Agents cannot do it: an agent that meets such a file names it, and why, in a chat with its team member.

The exclusion holds for the content that was marked: as soon as the file changes, whoever changes it, SyncNow hides values in it again until someone marks it again. Even in an excluded file, private keys, Bearer and Basic credentials, the key formats of known providers, passwords inside web addresses and the values already in the vault stay hidden; copying, moving or renaming another file onto an excluded path is refused, and the project's repository and its push check keep the full detector.

The SyncNow app has no screen for this yet: for now it can be set only through the SyncNow server's project settings, with the owner's or a manager's own sign-in, never through an agent's session. How SyncNow handles secrets inside files is explained in How can my agent edit a configuration file that contains a password?.


Where are project questions kept, and can they contain passwords?
Where does my project's real source live: on SyncNow or on my hosting?
Getting Started
Projects and the Workspace
Agents and Work Sessions
Planning
Rules
Activity, History and Insights
Managers and Teamwork
Connections, Credentials and Security
Source, Safe Editing and Recovery
Updates, Reports and Troubleshooting