Lucidlane connects to your Linear workspace so each client gets a portal for their requests while your team keeps working in Linear. This page covers connecting, what Lucidlane can access, how it shows up in Linear, and how to disconnect.
Start with the first-portal checklist to plan your pilot, or browse the FAQ.
1. Connect your workspace
- Sign in to the Lucidlane console at console.lucidlane.app. You need the admin role in your Lucidlane account.
- Open Settings, go to the Integrations tab and click Connect on the Linear card.
- Linear asks you to authorize Lucidlane for your workspace. A Linear workspace admin has to approve it, because Lucidlane is installed as an app.
- You’re sent back to the console and Lucidlane starts syncing your Linear workspace, creating an unpublished portal for each Linear Customer. Review the portal’s access and visibility settings before publishing it.
To have someone else connect it, send them the install link console.lucidlane.app/connect/linear. It asks them to sign in first.
2. What Lucidlane can access
Lucidlane is installed as an app, not with anyone’s personal login, so the connection keeps working if the person who connected it leaves. It requests these permissions:
| Permission | Why |
|---|---|
read | Read issues, statuses, labels and comments to show them in portals. |
write | Update issues, for example when a client replies. |
issues:create | Create an issue when a client sends a request. |
comments:create | Post client replies as comments. |
customer:read, customer:write | Each portal maps to one Linear Customer, and requests are recorded as customer requests. |
initiative:read | Show initiatives on portal roadmaps. Read only. |
app:assignable, app:mentionable | Let your team assign or mention Lucidlane in issues. |
Lucidlane never asks for admin access.
3. How Lucidlane appears in Linear
- Lucidlane shows up as an app with its own name and icon.
- A client’s request or comment is posted with their name, labelled “Name (via Lucidlane)”.
- Anything written by Lucidlane’s AI features is marked as automated.
- Linear stays your system of record. Lucidlane reads from and writes to it, and doesn’t keep a separate tracker.
4. Portals and what clients see
- Each Linear Customer gets its own portal, on a Lucidlane subdomain or your own domain. New Customers you add in Linear get an unpublished portal too.
- Requests from a portal become Linear issues linked to that Customer and routed to your triage.
- Clients see requests linked to their Customer, narrowed by project and status settings. Requests without a project can still appear. Label settings control visible tags, and priority settings control intake choices; they do not hide whole requests.
Comments on shared issues can sync into the portal. Treat those threads as client-facing and keep internal-only discussion elsewhere. Review descriptions, attachments and comments using a client account before sharing access.
5. Disconnect
In the console, open Settings, go to Integrations, click Manage connection on the Linear card and choose Disconnect. Lucidlane removes its stored connection and attempts to revoke its Linear access and syncing stops. You can also remove the app from your Linear workspace settings. Data Lucidlane already synced stays with your account until it closes. To have it deleted sooner, email support@lucidlane.app. See the Privacy Policy for details.
6. Help
Questions about the Linear connection? Email support@lucidlane.app. Use of Lucidlane is covered by our Terms of Service and Privacy Policy.