# Writer 7 and later If you are running Writer 7, you will need to make some additional settings in Writer settings. ### Key Store values to be added (if not already added) Before doing this, you will also need to add new "Key Store" values: | Key name | Key Value | | --------------------- | ----------------------------------------------------------- | | WRITER\_RESOLVER\_URL | \* | | WRITER\_ROUTER\_URL | \* | \*) Depending on environment typ (production, stage) change `prod` to `stage` if necessary. \ \*\*) The URL is dependent on Naviga deployments per region and the actual link will differ. ### Writer configuration / settings Flip the switches for "Use SaaS Endpoints …" as well as "Use proxy for Writer requests". Fill in the key values as stated below. ``` You will need the folllowing "keys": Writer Resolver URL ${DBKS:WRITER_RESOLVER_URL} Writer Router UR ${DBKS:WRITER_ROUTER_URL} ``` ![](https://1581899417-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Ll6-u036-4GP1c0Pgyo%2F-MZR2OFlllWd0r81y2JE%2F-MZR5rDcNZSX7pWy6AqT%2Fimage.png?alt=media\&token=6dacf991-2c89-4464-a410-c1727fc13370) --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.navigaglobal.com/dashboard-writer/5.0.0-3/admin/config/writer-7-and-later.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.