Getting started

This guide takes you from an empty workspace to your first grounded answer: you connect a source, Liddr learns from it, and you Ask a question with citations. Most of the time is Liddr syncing your source in the background — you can keep working while it does.

Before you start

You need access to your workspace. Connecting a source is an admin action, so if you are not an admin, ask your Liddr administrator to add the source for you — then pick up from step 4.

1. Sign in to your workspace

Open your workspace and sign in. You land on the home view, where the main surfaces — Know, Signal, Forge, and Settings — are in the navigation.

2. Connect your first source

An admin connects a source under Settings → Connections:

1. Choose a source to start with — Jira, GitHub, or Confluence are good first picks, because they carry a lot of your organization's structure and work.
2. Enter the credentials for that source.
3. Run a quick Test to confirm Liddr can reach it, then save.

Pick a high-signal source first

Start with the system that holds the most of your team's structure and decisions. You can always add more sources later — Liddr composes across all of them into one graph.

3. Liddr syncs your source

Once a source is connected, Liddr syncs it automatically in the background and keeps it current as your tools change — no manual steps, no scheduling. Each item becomes part of your shared knowledge graph, ready to be searched by meaning and cited in answers. The first sync of a large source can take a little while; you can leave the page and come back.

4. Ask your first question

1. Open Know.

2. Type a question about the source you just connected. Realistic examples:

   • "What are the open blockers on the billing project, and who owns them?"
   • "Summarize the decisions made about the new auth flow."
   • "Which pull requests touched the payments service in the last two weeks?"
   • "What's the current status of the onboarding redesign?"

3. Send it. The answer streams in.

Review the cited sources

Every claim Liddr makes is grounded. As the answer arrives:

• Inline citations mark each claim, and the references list at the bottom links to the exact source — the Jira issue, the pull request, the Confluence page.
• Open a citation to confirm it for yourself.
• If a banner flags unverified references, those were not found in the cited sources — treat them as unconfirmed.
• Use the suggested follow-up questions to keep exploring.

Try the answer modes

By default Know gives a thorough answer. Switch to concise for a quick reply or email to get a ready-to-send draft of the same answer.

5. See your Signal

1. Open Signal.
2. Choose a perspective that matches your role (for example developer, SRE, architect, PM, designer, or delivery manager) and a time window.
3. Generate the digest. Liddr returns a short narrative of what changed, what's at risk, the decisions made, and what to look at next — with each item linked to its source.

Where to go next

You now have a working loop: connect a source, ask, and read your Signal. From here:

• Connect more sources under Settings → Connections to enrich the graph.
• Set up MCP connectors for any personal or sensitive data you want reachable at answer time without bringing it into the shared graph.
• Try an Initiative to drive a piece of work through SDLC stages and, optionally, open a pull request with Build.

Related

• What is Liddr
• Core concepts
• Connectors overview
• Know