> ## 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.

# 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.

Adding a member is not only about creating a login. A useful invite also gives the person the right product areas, actions, and record scope for their job without exposing unrelated work.

Team collaboration is a Teams capability in the current entitlement model. Owners and admins manage members and access from the Teams and Owner surfaces when their permissions allow it.

## Before you invite someone

Decide what the person needs to do, not which role name sounds closest. A salesperson may need Sales and Agreements, a finance user may need Accounting and Agreements with Inventory read access, and a support user may only need Support.

Lynka evaluates several layers together:

1. workspace plan and active subscription state
2. areas allowed by the plan
3. areas enabled for the workspace
4. role defaults
5. user-level area access or overrides
6. action permissions
7. record scope

A person can therefore have a valid workspace membership and still not see a particular area.

## Invite the member

<Steps>
  <Step title="Open member management">Use **Settings > Teams** or the Owner workspace member controls, depending on the current navigation available to your role.</Step>
  <Step title="Start the invite">Choose the invite or add-member action.</Step>
  <Step title="Enter the member identity">Provide the email or user details requested by the invite flow.</Step>
  <Step title="Choose role and access">Select the role or access profile that matches the person's responsibilities. Review area access rather than assuming the role name grants everything.</Step>
  <Step title="Send the invite">Send the invitation and wait for the member to activate it.</Step>
  <Step title="Verify effective access">After activation, confirm the user can see the correct areas and records and is blocked from actions they should not perform.</Step>
</Steps>

## Plan limits and pricing

Do not use this documentation as a seat-price table. Included seats, additional seat pricing, promotions, and billing terms can change. Use [Plans and capabilities](/workspace/plans) to understand feature progression and the [current pricing page](https://lynkacrm.com/pricing) for live commercial terms.

## If the invited user sees too much

Review user-specific area access and data scope. A broad role grant can be narrowed by a user-level deny where the resolver supports it. Record scope also determines whether a person sees only owned records, a team set, or broader workspace data.

## If the invited user sees too little

Check that the workspace plan includes the area, the area is enabled, the role default allows it, no explicit deny is present, and the person has the action permission required for the specific operation.

## Related articles

* [Roles and permissions](/teams/roles-permissions)
* [Control product area access](/teams/access/product-areas)
* [Record scope and visibility](/teams/access-scopes)