# Importing and exporting operators

Create or update operator accounts from CSV and export a filtered roster for review.

*Release 3.3 · admin, supervisor*

**Settings › Account › Operators › Import** · **Settings › Account › Operators › Export**

## What it is

Operator import creates or updates several accounts from a CSV file. Export downloads a roster using your current operator filters. Together they support bulk administration and access reviews.

## Who uses it and why

Users with the **Settings** or **Manager** role and the required operator permissions use import for onboarding and bulk changes, and export rosters to review the accounts, roles and assignments they manage.

## Where to find it

With the **Settings** or **Manager** role and the required operator permissions, open **Settings › Account › Operators** and choose **Import** or **Export**. The import window provides **Download Sample File with template only** and **Download Sample File with all columns**.

## How it works

1. Download the sample that matches your workflow.
2. Keep its column headings and fill in the operator details.
3. Upload the CSV through **Import**, then review the preview and resolve validation errors.
4. Submit the import and follow its progress.
5. Refresh the directory and verify the resulting accounts.

An existing **Operator ID** targets an update. New accounts follow creation validation and can use a **Template**. Roles, channels, subsites, skills, teams and operational settings are available through the full-column workflow.

For export, first apply search and filters such as role, status, channel, team, skill or subsite, then choose **Export**.

## Configure it

Use the samples and the import window's help to check accepted columns and values. Keep the sample's headings exactly as supplied, including case and spacing. Review any column assignments shown by the preview.

Template import uses an existing website template to supply new-account settings and assignments. The full-column option lets you supply those choices directly. The import limit is normally 1,000 records; Powerfront support can change this for you.

### Fields

| Field | Where | Required | What it is for |
|---|---|---|---|
| Operator ID | Settings › Account › Operators › Import | Yes | Identifies an existing account to update; new accounts follow the creation workflow. |
| Template | Settings › Account › Operators › Import | Unknown | Selects an existing operator template for new-account import. |

### Permissions

| Permission | Lets you |
|---|---|
| Manager | Import and export operators within account authority. |
| Settings | Import and export operators when the operator administration controls are available. |
| Operators | Allow operator administration. |

## Limits and good to know

Existing-account import preserves the account's current default website. A supplied default channel must be one of the selected channels. Selecting all channels is treated as unrestricted access in the import flow.

Validation can reject a batch before any changes. A failure during processing can leave earlier rows applied. Review the processed count and actual operator list before retrying.

Import cannot grant privileges beyond the importing account's authority. Referenced templates, teams, skills and channels must be valid for the website.

## Depends on and works with

### This feature uses

- **Requires** [Operator accounts](ADM-007.md): Import and export use operator account creation, update and directory functions.
- **Configured in** [Subsites](ADM-003.md): Imported subsite assignments must match the website's subsite catalogue.
- **Configured in** Admin settings and feature switches (managed by Powerfront): Website operator limits also apply when importing new accounts.
- **Configured in** [Roles and permissions](ADM-008.md): The importing user's authority limits permitted roles and accounts.
- **Configured in** [Operator templates](ADM-011.md): A selected operator template supplies the initial roles, settings and assignments for new imported accounts.
- **Configured in** [Teams](ADM-013.md): Imported team assignments must match teams available in the website.
- **Configured in** [Skillsets and skills-based routing](CHAT-007.md): Imported skill assignments must match skills available in the website.
- **Configured in** [Departments](CHAT-006.md): The floor channel catalogue determines which imported channel assignments are valid.
- **Configured in** [Operator sign-in network and email restrictions](SEC-028.md): Email-domain admission rules apply during validation.
- **Related** [Website, channel and subsite access](ADM-009.md): Review scoped access rules before importing or reviewing website, channel and subsite assignments.
- **Related** [Operator settings](ADM-010.md): Review operator settings and capacity limits before filling the full-column import.

### Used by

- **Configures** [Operator accounts](ADM-007.md): CSV import can create operator accounts and change their settings or status in bulk.
- **Configures** [Website, channel and subsite access](ADM-009.md): Operator import can set website-specific channel, subsite and skill assignments in bulk.
- **Enhances** [Operator templates](ADM-011.md): Operator import can apply a template to new accounts.

## FAQ and troubleshooting

### Should I start with an exported roster or a sample?

Use a sample to check the supported import format. Export is useful for reviewing existing account IDs and assignments.

### Why does a row fail on its default channel?

Include the default channel among that row's selected channels.

### Can I change an existing operator's default website by import?

This update workflow preserves the existing default website. Change it through the operator editor.

### The import failed halfway through. Can I upload it again?

First verify which rows were applied. Correct or remove processed new-account rows and use existing operator IDs for intended updates.

### Why is my export smaller than expected?

Export uses your operator search and filters, as well as your account's available scope.