{"version":"2.1.236","anchor":"saving-database-documents-to-disk-asks-for-the-exact-path-an","canonical_anchor":"saving-database-documents-to-disk-asks-for-the-exact-path-an","heading":"Saving database documents to disk asks for the exact path, and re-checks it at run time","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/saving-database-documents-to-disk-asks-for-the-exact-path-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Saving database documents to disk asks for the exact path, and re-checks it at run time\n\nApproving a database read that saves files now names the exact destination and flags paths outside your workspace.\n\n**What**\n\nBecause a read that saves files writes to your disk, the approval names the exact destination path and flags destinations outside the session's working paths as needing your own approval rather than automatic approval.\n\n**Details**\n\n- The approved destination is remembered for the call, and execution refuses if `out_dir` was added, removed, or changed after you approved it.\n- The result line becomes a count of documents saved under the directory plus a skipped count.\n- The parameter is only offered when the artifact database action itself is available in the session.\n\n**Evidence**\n\n`read_db saves only to local directories \u2014 out_dir names a network path`\n\n- Area: Permissions\n- Names: `out_dir`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}