> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/v1/how-to-guides/workflow/ieees-ecf-integration-for-camera-ready-submissions.md).
# IEEE's eCF Integration for Camera-Ready Submissions
For OpenReview to integrate with IEEE's Electronic Copyright Form (eCF), the program chairs will need to know their IEEE Publication Title and IEEE Art Source Code.
## Author Console
Go to the Authors group (in Edit mode) and add the following properties to the **Group UI Code** at the bottom of the group page:
1. showIEEECopyright: true,
2. IEEEPublicationTitle: “”,
3. IEEEArtSourceCode:
Save the changes, and the “CopyRight Submission” button will appear in the console for authors of the Accepted Submissions only. This means decisions must be posted and the Post Decision was run.
## Testing
If the program chairs want to test submitting the copyright form, they can do so with an Accepted submission. They’ll need to delete the submitted form on the IEEE side afterwards.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.openreview.net/v1/how-to-guides/workflow/ieees-ecf-integration-for-camera-ready-submissions.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.
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.
