> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/feature-documentation/designing-and-running/personas/working-with-personas/batch-and-bulk-operations.md).
# Batch & Bulk operations
Batch and bulk operations allow you to update multiple personas at the same time:
* **Batch** changes use the Editor interface and offers more common operations
* **Bulk** changes requires the use of a spreadsheet which is exported and imported
## Batch changes
{% embed url="" %}
When you're building an exercise, you rarely need to create every persona from scratch. You can import personas from another project, from a file, or from our asset library Ventura.
But personas built for one scenario (e.g. a flood response) won't always fit into a different one (e.g. a fire at a train station). You might find names, roles, handles, and channels will need adjustments once they're imported.
Rather than opening each persona individually, the `Personas` tab gives you two ways to make these adjustments across many personas at once:
### Replace persona
Swap one persona for another (e.g. matching an imported persona to an existing role) and choose, field by field, whether to keep the original's details or take the new one's (profile image, handle, name, email, location, and social/banner images can each be kept or replaced independently).
### Batch
Select multiple personas in your library and edit shared properties for all of them in one operation (disposition, affilation, which social channels are active, tags, and who's allowed to impersonate the persona).
## Bulk changes
You might also find it easier to create and edit personas via a spreadsheet.\
To create personas this way, export an empty persona library, fill in the intended columns, and reimport.
The spreadsheet you're likely to want is `Persona details`, but you can edit all kinds of persona variables from the list in the screenshot below:
---
# 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://helpdocs.conducttr.com/feature-documentation/designing-and-running/personas/working-with-personas/batch-and-bulk-operations.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.
