Connect Lark — Tasks and Wiki Docs as Claim Evidence

If your R&D team lives in Lark — tasks for who did what, wiki pages for how the approach evolved — that work already looks a lot like SR&ED evidence. You shouldn’t have to export it by hand. SREDr can connect to international Lark and gather it for you.

One connection, two kinds of work

From a claim’s Sources tab, connect Lark and choose what to include:

• Tasks — shared task lists, plus tasks that aren’t on any list yet.
• Wiki spaces — documents under a space, pulled in for the claim period.

Pick what matches the claim year, then run gather. Evidence shows up ready for eligibility review and grouping like any other connected source.

Sign in or use an app credential

You can connect in two ways:

1. Connect — a team member signs in with Lark. Best when you want personal tasks included.
2. App ID & App Secret — an organization app credential. Useful for a durable connection to shared tasks and wiki spaces the app can read.

Both are read-only. SREDr lists what you select and imports content for the claim; it does not send messages, edit tasks, or change wiki pages.

Built for how Lark is actually used

Many teams track delivery in Tasks and keep design notes in Wiki. This connector follows that split: task work and wiki docs — not chat or Base. Comments on tasks count as supporting activity, so progress notes and review threads can add context beyond the task title.

Where to look

1. Open a claim → Sources → Lark.
2. Sign in with Connect, or enter App ID & Secret if your admin has set that up.
3. Configure → select the tasks and wiki spaces to include.
4. Run gather and review new evidence under Evidence.

If something you expect is missing, check that the right resources are selected and that the claim dates cover when the work was updated.