> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Collaboration

> Use Octoparse team workflows to share tasks, standardize extraction work, and manage data collection across users.

Collaboration features help teams build, run, review, and maintain extraction tasks together. They are useful when multiple people need access to tasks, exported data, or recurring workflows.

Use collaboration workflows when data collection is part of a shared business process rather than an individual one-off task.

## What teams collaborate on

Teams commonly collaborate on:

* Task building and review
* Template or workflow reuse
* Cloud runs and [schedules](/docs/platform/schedules)
* Export destinations
* Data quality checks
* Troubleshooting failed runs
* Documentation for task ownership and maintenance

## Typical team workflow

<Steps>
  <Step title="Create the task">
    A builder creates the workflow, selects fields, and configures run settings.
  </Step>

  <Step title="Review sample output">
    A reviewer checks whether the fields, records, and export format meet the team's needs.
  </Step>

  <Step title="Set ownership">
    Assign responsibility for monitoring, updating, and troubleshooting the task.
  </Step>

  <Step title="Automate runs or exports">
    Configure schedules and destinations if the workflow needs recurring delivery.
  </Step>

  <Step title="Monitor and improve">
    Use [logs](/docs/platform/logs-and-events), run history, and output checks to keep the task reliable over time.
  </Step>
</Steps>

## Best practices

| Practice                             | Why it helps                                         |
| ------------------------------------ | ---------------------------------------------------- |
| Use clear task names                 | Makes tasks easier to find and maintain              |
| Document target websites             | Helps others understand what the task collects       |
| Keep field names consistent          | Reduces downstream mapping issues                    |
| Review changes before scheduled runs | Prevents broken workflows from running automatically |
| Separate raw data from analysis      | Keeps exports predictable                            |
| Assign task owners                   | Avoids unclear responsibility when failures happen   |

## Collaboration roles

A team workflow may involve:

* A task builder who configures extraction logic
* A reviewer who validates output quality
* An operator who monitors schedules and runs
* A data owner who manages downstream use
* An admin who manages account, access, and billing settings

<Note>
  The exact collaboration and permission options depend on your Octoparse plan and account setup.
</Note>