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

# Assign and reassign work across your team

> Use Lynka ownership and assignment to make responsibility clear for leads, deals, tickets, and other team work without confusing ownership with record visibility.

Assignment answers a practical question: **Who is responsible for what happens next?**

In Lynka, ownership and visibility are related but separate. A user can see a record without owning it, and changing the owner does not automatically rewrite the entire access policy.

## Assign early enough to create accountability

A Lead with no owner can sit untouched even if the whole team technically has access to it. Assign responsibility when the business expects one person to take the next action.

Lynka's automation catalog includes attention rules for active Leads with no owner and Tickets with no assignee because unowned work is easy to lose.

## Leads

Assign the Lead to the person responsible for qualification and follow-up. Their activities and next actions should then reflect the real sales process.

If the Lead later qualifies, make sure the created Deal has the appropriate commercial owner.

## Deals

The Deal owner is responsible for moving the opportunity through the pipeline and recording a clean final outcome. Reassign the Deal when responsibility genuinely changes, not simply because another teammate helped with one activity.

## Tickets

Ticket assignment should make the service owner clear. If the assigned person cannot resolve the issue, reassign or escalate according to the support process rather than leaving the ticket in an ambiguous shared queue.

## Reassign when someone is unavailable

If a team member is away or leaves the company, review their open work before removing access.

Look for:

* open Leads with future follow-up
* open Deals and expected close dates
* unresolved Tickets
* tasks and activities
* approvals or owner-specific review work

Reassign the operational records first, then remove or narrow access.

## Managers and team scope

A manager can have visibility across team records when the access model allows it without becoming the owner of each record.

That is usually the cleaner model: the seller owns the Deal, the manager can review the team's Deals, and the owner can use wider reporting when permitted.

## Do not use ownership as a security setting

If somebody should not be able to see a record type, fix their area access, permissions, or record scope. Simply changing the record owner is not a reliable substitute for access control.

<Card title="Understand record scope" href="/teams/access-scopes" icon="eye">
  Learn why Mine, team, and workspace visibility should be configured separately from assignment.
</Card>
