Skip to main content
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

1

Open member management

Use Settings > Teams or the Owner workspace member controls, depending on the current navigation available to your role.
2

Start the invite

Choose the invite or add-member action.
3

Enter the member identity

Provide the email or user details requested by the invite flow.
4

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

Send the invite

Send the invitation and wait for the member to activate it.
6

Verify effective access

After activation, confirm the user can see the correct areas and records and is blocked from actions they should not perform.

​
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 to understand feature progression and the current pricing page 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.
Last modified on September 7, 2026