Skip to main content
Lynka is built for small teams as well as solo owners. A small team already has real coordination problems: one person owns a Lead, another handles the Quote, finance records the Payment, operations receives stock, and the owner wants to understand the whole business without doing every task personally. Teams is the layer that makes those responsibilities shareable without turning every user into an administrator.

​
Teams is more than extra logins

Lynka separates six concepts that are easy to confuse: Membership answers whether the person belongs to the workspace. Product area access answers whether they can open Sales, Agreements, Inventory, Accounting, Support, Marketing, LeadGen, or Reports. Action permissions answer what they can do, such as assigning a Lead, posting an Invoice, reversing a Journal, or managing Teams. Record scope answers which records they can see, such as Mine, a team, or wider workspace data where allowed. Ownership answers who is responsible for a specific record. Team membership groups people so the business can organize collaboration and team-level scope. These layers let a five-person business stay simple without becoming careless about customer and financial data.

​
A practical small-team model

An owner can keep broad visibility. Sales users can work Leads, Deals, Activities, and commercial documents. Finance can work Agreements and Accounting. Operations can work Inventory. Support can work Tickets. One person can also wear two hats and belong to more than one team.

See a five-person example

Start with a realistic small business, then adapt the access to your own people.

​
Role defaults are a starting point

The live role model includes defaults for Owner, Admin, Finance, Marketing, Support, Sales, Rep, and Member patterns. Do not treat the role name as the final access decision. Plan capabilities, enabled product areas, user overrides, action permissions, and record scope still apply.

​
Managers do not need Admin

A manager can receive team-level visibility and the actions needed to supervise work without receiving every workspace or finance permission. Manager visibility shows how to widen review while keeping sensitive controls separate.

​
Ownership keeps work from disappearing

Assign Leads, Deals, Tickets, and other supported records to the person expected to act next. Team access can let several people see the record, but somebody should still own the responsibility. Lynka’s attention automation includes rules for unowned Leads and unassigned Tickets because shared access without responsibility can still produce missed work.

​
Approvals add control where it matters

Use approvals when a second decision is worth the delay. They are a collaboration control, not a requirement to make every small action bureaucratic.

​
When someone leaves

Review their open work, reassign responsibility, update team memberships, and only then remove workspace access. Historical activity can remain part of the business record after the person is no longer active.

Invite a member

Add a person and then configure access deliberately.

Assign team work

Use ownership without confusing it with visibility.

Product area access

Control which parts of Lynka someone can open.

Record scope

Understand Mine, team, and workspace visibility.

​
Plan availability

Team collaboration is part of the Teams capability model. Use lynkacrm.com/pricing for current included users, pricing, and commercial packaging.

Run Lynka with a small team

Set up Lynka for an owner and a small team by separating product access, action permissions, record visibility, ownership, team membership, and approvals.

Members and responsibility

Invite a member to your Lynka workspace

Invite a teammate, choose the right access level, and understand how plan access, installed areas, role defaults, and user overrides affect what they see.

Create and manage teams

Group workspace members into teams, assign team managers, and use team membership for collaboration and record scope without changing record ownership.

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.

Give managers visibility without giving full admin access

Configure Lynka so managers can review team work and reporting while sensitive product areas and administrative actions remain separately controlled.

Remove a team member without losing track of their work

Review ownership, open records, tasks, approvals, team membership, and access before removing a person from a Lynka workspace.

Roles and access

Control which product areas a user can access

Understand plan access, workspace-enabled areas, role defaults, and user-level area overrides for Sales, Accounting, Inventory, Support, Marketing, and Reports.

Customize action permissions

Control create, edit, assign, post, export, reopen, void, and other sensitive actions separately from broad product area access.

Product access and record scope

Separate which product areas a person can open from which records they can see inside them.

Approvals

Use approvals in Lynka

Understand approval requests, reviewer access, plan requirements, and why approval should gate a sensitive action instead of replacing the source workflow.

Last modified on September 7, 2026