01
Connect the workspace
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
IntegrationLinear integrationAvailable
Delivery signal beside the goal.
Keep the goal and the delivery signal in the same conversation.
- Search recent Linear issues without leaving the goal.
- Attach the issues that matter as context chips.
- Linear stays the delivery system; Perelan only reads.
Verified integration behavior only. External tools remain their own systems of record where applicable.
Runtime path
- 01Connect
- 02Choose team
- 03Search recent issues
- 04Link to goal
Operational flow
How the connection works in Perelan
Start with identity and setup, then follow the data direction, permission check, source record, and fallback state.
02
Choose the teams that matter
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
03
Find recent work without leaving the goal
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
04
Respect the integration boundary
This integration is described through setup ownership, identity mapping, data direction, permission checks, and fallback states so a connected tool does not become an accidental authority.
Runtime path
- Connect
- Choose team
- Search recent issues
- Link to goal
- Open in Linear
Relevant product paths
Controls and boundaries
Can we choose specific Linear teams?
Yes. Team selection is part of the integration settings.
Does Perelan create or edit Linear issues?
This page does not claim issue creation or editing. Linear remains the delivery system.
How current is issue status?
The integration reads recent issue data when refreshed or queried; it is not marketed as an unverified webhook sync.
Can employees see issues they cannot access in Linear?
Perelan should not be used to broaden Linear access. Configure and share linked context deliberately.
Does this bypass Perelan permissions?
No. The marketing examples are compressed, but the product path still checks the acting user, role, group scope, and domain permission before data is shown or changed.
Is the page showing real customer data?
No. The product demonstrations use fictional names, roles, dates, and values so the workflow is clear without exposing real people or companies.