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

# Teams, Permissions, and LSP Hierarchy

> Understand team structures, permissions, assignment visibility, operational hierarchy, and LSP workflows inside the Ollang Project Management Dashboard.

## Overview

The Ollang Project Management Dashboard supports:

* internal operational teams,
* external linguists,
* translation agencies,
* dubbing studios,
* and multi-layered localization workflows.

The platform separates operational users into:

* Project Management users,
* and Editor / LSP users.

This separation allows organizations to:

* control visibility,
* manage assignments,
* organize localization operations,
* and securely coordinate multilingual workflows.

***

# The Two Main Operational Environments

<CardGroup cols={2}>
  <Card title="Project Management Dashboard">
    Used for operational oversight, order creation, billing, analytics, workflow management, and project organization.
  </Card>

  <Card title="Editor / LSP Interface">
    Used for subtitle editing, dubbing review, translation operations, and assignment-based localization workflows.
  </Card>
</CardGroup>

# Team Invitation Types

Organizations can invite multiple operational user types.

<CardGroup cols={2}>
  <Card title="Team Member" icon="users">
    Internal operational users working inside the Project Management Dashboard.
  </Card>

  <Card title="Editor" icon="file-edit">
    Linguists or reviewers working inside the Editor Interface.
  </Card>

  <Card title="Translation Agency" icon="building-2">
    External localization vendors managing multilingual operations.
  </Card>

  <Card title="Dubbing Studio" icon="mic-2">
    Professional dubbing vendors handling voice production workflows.
  </Card>
</CardGroup>

***

# Project Management Users

## Overview

Project Management users operate inside:

* the Ollang Project Management Dashboard.

These users manage:

* Folders,
* Projects,
* Orders,
* assignments,
* billing,
* analytics,
* and workflow operations.

***

# Project Management Roles

The platform supports operational permission structures including:

* Owner
* Admin
* Project Manager
* Team Member

***

# Permission Structure

## Core Permissions

Permissions may include:

<CardGroup cols={2}>
  <Card title="Create Orders">
    Allows users to create localization workflows and operational Orders.
  </Card>

  <Card title="Manage Team">
    Allows users to invite and manage operational users.
  </Card>

  <Card title="Access Billing">
    Allows users to view analytics, invoices, billing details, and payment-related operations.
  </Card>

  <Card title="View Access">
    Allows operational visibility into organizational workflows and Projects.
  </Card>
</CardGroup>

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/image.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=3a0e72f249f96705bf5952e69a83e24c" alt="Image" width="948" height="558" data-path="images/image.png" />
</Frame>

***

# Access Billing Clarification

Users with Access Billing permissions may view:

* invoices,
* analytics,
* payment information,
* and operational financial data.

However:

* general credit visibility remains visible operationally across workflows.

***

# Folder-Based Notification Logic

Notification behavior operates primarily at:

* Folder level.

Example:

```text theme={null}
Project Manager A assigned to Folder A
        ↓
Team Member B creates Order
        ↓
Order completes
        ↓
Both users receive notification
```

***

# Visibility Rules for Project Management Users

Project Management users generally have visibility into:

* all Folders,
* all Projects,
* and organizational workflows.

However:

* notification ownership operates through Folder assignment structures.

***

# Editor / LSP Users

## Overview

Editors and linguists operate inside:

* the Editor / LSP Interface.

These users focus on:

* subtitle editing,
* transcription review,
* dubbing workflows,
* translation refinement,
* and operational delivery.

***

# Important Visibility Rule

<Info>
  Editors do not see all Projects or organizational workflows.
</Info>

Editors only see:

* explicitly assigned Orders.

Assignments operate primarily at:

* Order level, not:
* Project level.

***

# Example Assignment Visibility

```text theme={null}
Folder contains:
- 10 Projects
- 200 Orders

Editor assigned:
- 5 Orders

Result:
- Editor only sees assigned Orders.
```

***

# LSP Hierarchy

The platform supports a multi-level localization hierarchy.

```text theme={null}
LSP Admin (Editor)
        ↓
LSP Project Manager
        ↓
LSP Linguist
```

# LSP Admin

LSP Admins can:

* manage localization operations,
* assign Orders,
* onboard linguists,
* and coordinate multilingual workflows.

LSP Admins typically act as:

* operational vendor managers.

***

# LSP Project Manager

LSP Project Managers can:

* coordinate operational assignments,
* manage delivery pipelines,
* and oversee linguist workflows.

These users commonly manage:

* multilingual delivery operations,
* reviewer coordination,
* and operational execution.

***

# LSP Linguist

LSP Linguists:

* edit assigned Orders,
* refine localization output,
* and deliver finalized workflows.

They only see:

* Orders assigned to them.

***

# Translation Agencies and Dubbing Studios

## Overview

Translation Agencies and Dubbing Studios may:

* create internal users,
* assign operational tasks,
* and coordinate multilingual delivery pipelines.

This allows vendors to:

* manage their own operational structures inside Ollang.

***

# Studio Dubbing Vendor Workflows

Studio vendors may:

* upload dubbing vocals,
* upload final mixed outputs,
* upload Mixmaster files,
* and coordinate operational dubbing delivery.

However:

* delivery behavior depends on Order type.

***

# Important Studio Dubbing Rule

<Warning>
  Studios cannot deliver isolated vocals-only files without sufficient operational audio structure.
</Warning>

Delivery workflows require:

* either final mixed outputs,
* or operationally compatible audio assets.

***

# Interface Switching

Project Management users may also:

* switch into the Editor Interface.

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/a2.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=10722ebe147b7bb3ddc951f98a8ad758" alt="A2" title="A2" className="mx-auto" width="414" height="334" data-path="images/a2.png" />
</Frame>

<Frame>
  <img src="https://mintcdn.com/ollang/a4ucNOBUQRWRvsN6/images/a3.png?fit=max&auto=format&n=a4ucNOBUQRWRvsN6&q=85&s=f64c85a39eda69885b79335e3a92825d" alt="A3" width="332" height="328" data-path="images/a3.png" />
</Frame>

This allows:

* operational review,
* subtitle editing,
* dubbing review,
* and assignment-level editing workflows.

***

# Important Operational Clarification

A Project Management user switching into the Editor Interface only sees:

* Orders assigned to them operationally inside the Editor environment.

Visibility still operates through:

* Order-level assignment logic.

***

# Example Multi-Team Workflow

```text theme={null}
Project Manager creates AI Dubbing Order
        ↓
Order assigned to Translation Agency
        ↓
Agency Project Manager assigns Linguist
        ↓
Linguist edits subtitles
        ↓
Project Manager receives completed delivery
```

***

# Important Operational Notes

<AccordionGroup>
  <Accordion title="Can organizations onboard their own linguists?">
    Yes. Organizations may onboard internal reviewers, agencies, editors, and dubbing studios.
  </Accordion>

  <Accordion title="Do Editors see all Projects?">
    No. Editors only see explicitly assigned Orders.
  </Accordion>

  <Accordion title="Can translation agencies create internal users?">
    Yes. Agencies may create and manage their own operational users.
  </Accordion>

  <Accordion title="Can dubbing studios upload deliverables directly?">
    Yes. Studio workflows support uploaded dubbing assets and final delivery coordination.
  </Accordion>

  <Accordion title="Can Project Management users switch to the Editor Interface?">
    Yes. Project Management users may access the Editor Interface for operational review workflows.
  </Accordion>

  <Accordion title="Do assignments operate at Project level or Order level?">
    Assignments primarily operate at Order level.
  </Accordion>
</AccordionGroup>