{"version":"2.1.247","anchor":"directory-trust-can-be-judged-strictly-from-saved-state","canonical_anchor":"directory-trust-can-be-judged-strictly-from-saved-state","heading":"Directory trust can be judged strictly from saved state","tier":"internal","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/directory-trust-can-be-judged-strictly-from-saved-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Directory trust can be judged strictly from saved state\n\nDirectory trust can now be decided strictly from saved state when the host serves your files.\n\n**What**\n\nBuilding the permission context is now asynchronous, and when the newer storage layout is in use and workspace files are served by the host it computes a strict-persisted-trust value that feeds both the deny rules and the list of additional working directories.\n\n**Details**\n\n- Requires storage version 5 and `hostFiles.serving(\"workspace\")` returning `\"host\"`.\n- In every other configuration the options object is empty and trust is decided exactly as before.\n\n**Evidence**\n\n`strictPersistedTrust`\n\n- Area: Permissions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}