Your client portal questions, answered.

Clients use their Lucidlane portal to send requests and check progress. Your team handles the underlying issues in Linear, so clients do not need to learn your internal issue workflow.

Each portal shows issues linked to its Linear Customer, with filters to narrow the view further. Check the Customer associations and use separate client accounts to verify what each person can see.

Comments on shared issues can sync into the client portal. Treat those threads as client-facing and keep internal-only discussion elsewhere. Before inviting clients, review the visible descriptions, attachments and comments using a client account.

Use a project filter to narrow the issues linked to the portal’s Customer. The Customer association still matters: selecting a project is not a substitute for linking the client’s requests. Status settings can also narrow visible requests. Requests without a project can still appear. Label settings control visible tags and priority settings control intake choices; neither hides whole requests.

Clients open their portal to see the status of their linked requests. Your team maintains the work in Linear rather than copying the same status into a separate client tracker.

Map each client to a Linear Customer, organize delivery in projects, and choose portal filters for the work that client should see. The multi-client guide walks through an example with two clients in the same workspace.

Yes. Client replies are posted as comments through the Linear connection, with the client’s name and a “via Lucidlane” attribution.

It is designed for agencies, studios and client-service teams already using Linear to deliver work for multiple clients. Each client relationship maps to a Linear Customer and its own portal.

A request sent through a portal becomes a Linear issue linked to that portal’s Customer and routed to your triage. Your team can then review and work on it in Linear.

Clients submit a portal request and follow its status while your team investigates in Linear. Keep clarification on that request, then ask the client to reply after testing the fix so you can agree whether it is resolved.

A portal can give a retainer client a place to submit follow-up requests and check existing work. Keep commercial scope and delivery commitments in your agreed process; a submitted request is not automatically an approved commitment.

The channels add-on is coming soon. Use portal requests for the current workflow.

Introduce the portal around an open request: show the client where to check progress and reply. Agree which conversations belong there, while keeping calls and general communication in your existing process. Automatic email intake is not part of the portal workflow described here; the channels add-on is coming soon.

Linear remains the system of record. Lucidlane provides the client-facing view and request entry point connected to it.

You need access to Lucidlane, a Linear workspace, a Linear Customer for the pilot client and the admins needed to authorize the connection. Prepare a sample request and decide which work that client should see.

The setup guide requires a Lucidlane account admin and approval from a Linear workspace admin. Lucidlane is installed as an app.

The connection requests access for reading and updating issues, creating issues and comments, working with Customers, reading initiatives, and making the app assignable and mentionable. The setup guide explains each scope; it does not request the admin scope.

Lucidlane is installed as an app rather than using a personal login. The app connection can continue working if the person who installed it leaves.

The product includes white-label branding and custom domains, alongside Lucidlane subdomains. Confirm the domain configuration for your pilot before sharing its URL with a client.

Check the Customer mapping, visible and hidden issues, client access, a new request, a reply and a status change. Confirm the result in both the client portal and Linear.

Disconnecting removes the stored connection and attempts to revoke Linear access and stops syncing. Already-synced data remains with the account until closure unless you request earlier deletion.

Lucidlane is a client portal for teams that manage client work in Linear. Clients can submit requests, follow their progress and reply through a branded portal while the delivery team works in Linear.

Yes. Lucidlane connects a Linear workspace and uses Linear Customers and issues to organize client portals and requests. Start by checking whether that matches how your team works.

Create a Lucidlane account, connect your Linear workspace and choose one client for your first portal. The setup guides cover the connection and a checklist for testing the request workflow.

Lucidlane charges for published client portals and includes unlimited team members. Check the pricing page for the current base plan, included portals and additional portal rate.

Billing counts published portals; draft and archived portals do not count. Review the billing explanation on the pricing page before publishing.

The AI assistant is an optional add-on. The core workflow is a client portal connected to Linear requests, replies and status updates.

Choose one client and verify the request-to-Linear workflow first. Then compare the effort spent relaying status updates and ask whether the client can find their requests and understand the next step.