> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/whats-new/impersonation-mode-managing-print-campaigns-on-behalf-of-agents.md).
# Impersonation Mode: Managing Print Campaigns on Behalf of Agents
**Overview**\
We’re excited to announce that admins can now create and manage print campaigns while impersonating agents.
**What’s New**
* **Print Template Collaboration:** Admins can now collaborate with agents on print templates using impersonation mode.
* **Agent Placeholders:** Impersonation now pulls in agent-specific placeholder data, ensuring the correct information appears when managing agent print campaigns.
* **History Tabs:** When viewing template history, print templates are now organized into two tabs for easier access:
* **All:** Displays all print templates, including those created by admins and agents.
* **My Designs:** Displays only the templates created by the specific user, allowing for a more focused and personalized workspace.
These updates reflect our ongoing commitment to improving your experience with print campaigns. If you have any questions or feedback, don’t hesitate to reach out—we’re here to help!
{% embed url="" %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.rechat.com/whats-new/impersonation-mode-managing-print-campaigns-on-behalf-of-agents.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 `automate deployments from our CI pipeline` 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.
.png?alt=media&token=556a8408-90fb-447b-93f6-b7bd1776567a)