/ Setup guide /

Your first client portal: a setup checklist

Choose one client, connect Linear and verify what the client can see, submit and reply to before sharing a Lucidlane portal.

Use this checklist to set up and test your first client portal. For the exact connection steps and requested permissions, use the Linear setup guide.

1. Choose a client and prepare their work

  • Choose one client whose requests your team already manages in Linear.
  • Identify their Linear Customer and check which issues are associated with it. For a two-client example, see how to organize multiple clients.
  • Choose a test issue that should be visible, a comment suitable for the client and an issue belonging to another Customer.
  • Agree who will triage incoming requests and write client-facing replies.

2. Connect the workspace

Have a Lucidlane account admin start the connection from Settings → Integrations, with a Linear workspace admin available to approve the app. Follow the connection guide, then check that your chosen Customer has an unpublished portal.

3. Review the portal and its audience

  • Confirm the portal maps to the intended Linear Customer.
  • Choose the client-facing name, logo and portal address.
  • Review who can open the portal before sharing it.
  • If needed, narrow request visibility by project and status. Review requests without a project, visible labels, allowed intake priorities and optional fields separately.
  • Use a client account to check that the intended issue is visible and unrelated requests are excluded. Review the comments and attachments too; comments on shared issues can sync into the portal.

4. Test a complete request

  1. Submit a clearly labelled test request through the client portal.
  2. Find it in Linear and confirm the Customer association and triage destination.
  3. Send a client reply and check its comment and attribution in Linear.
  4. Change the test issue’s status in Linear and check the corresponding portal view.
  5. If a result is unexpected, resolve it before inviting the client. Record which side you changed and what appeared on the other side.

5. Publish and invite your client

After checking access and visibility, publish the portal and invite the intended client contacts. Published portals count toward billing. Give them the portal address and a short explanation of what belongs there. For example:

Use this portal for new requests and to check the progress of existing work. Include the context and desired outcome with each request. We’ll review it and agree priority and scope with you.

Adjust this message to your response expectations and service agreement.

6. Review the pilot before expanding

  • Can the client find a request and understand its status?
  • Does the team receive enough information to triage it?
  • Are visibility boundaries correct?
  • Are you spending less time manually relaying progress?
  • Have you checked published portal billing before adding more clients?

For a concrete example, see agency requests, bug reports or ongoing client work.