Skip to main content
Approvals give controlled actions a review step instead of relying on informal messages between a team member and an owner or administrator. Approval availability depends on workspace capability, collaboration access and permissions. A user can have access to the underlying product area without automatically being allowed to approve every sensitive action.

​
Where approvals appear

Approvals are available from Settings and Owner or Admin review surfaces where the current user is allowed to see them. The Owner workspace also groups operational reviews so pending decisions can be handled without searching each product area individually.

​
Request and decision are different actions

The person creating or changing a record can be different from the person who reviews the request. Keep the reason and affected record clear so the approver can make a decision without reconstructing the context from scratch.

​
Teams capability

Collaboration and approvals are plan dependent. If the approval surface is locked, check the current workspace capabilities and user access before treating it as an application error. Commercial packaging belongs on the current Lynka pricing page, not in a copied price table inside the docs.

Use approvals

Follow the approval workflow and review responsibilities.

Owner workspace

See where owners review approvals and operational attention.

Plans and capabilities

Understand the collaboration capability boundary.

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