> For the complete documentation index, see [llms.txt](https://docs.data.ca.gov/california-open-data-publishers-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.data.ca.gov/california-open-data-publishers-handbook/5.-get-publishing-approval.md).

# 5. Get Final Publishing Approval

* [ ] Are there changes flagged by your reviewers after [sharing in the previous step](https://github.com/CA-Data/docs-publishers-guide/blob/main/upload-the-dataset.md#share-private-dataset-for-review) on uploading the data?
  * [ ] **Yes** - implement the changes, and re-send for review and approval
  * [ ] **No** - receive final approval per your organization’s process and then set the visibility of the dataset to public - [see this guide on changing the visibility of a dataset](/california-open-data-publishers-handbook/reference/detailed-steps-for-uploading-data-to-the-portal.md#make-public-after-approval)
* [ ] :tada: Celebrate your publishing, here are some things you can do:
  * [ ] Work with your communications team to advertise your dataset on social media
  * [ ] Write a blog post incorporating an interesting analysis of the open data


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.data.ca.gov/california-open-data-publishers-handbook/5.-get-publishing-approval.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.