Write knowledge in pages
Build nested pages inside spaces for policies, onboarding, product decisions, runbooks, and support answers.
Workspace knowledge, built into the deck
Findset gives the people running your business one trusted place for policies, playbooks, product notes, and support answers. Structure the knowledge, attach its source files, and keep it connected to the work behind it.
More than file storage
Findset combines a team wiki, a document workspace, and a trusted file library, and keeps every source current.
Build nested pages inside spaces for policies, onboarding, product decisions, runbooks, and support answers.
Give people read, comment, edit, or manage access at the page level while workspace roles remain in force.
Search live records from StackDeck products and keep linked files pinned to the exact version another product uses.
Three kinds of knowledge
Each content type has a clear job, so everything in Findset has its place.
Rich pages with hierarchy, comments, labels, backlinks, watchers, revisions, and restore.
01PDF, Office, text, Markdown, and common image files with scanning, history, preview, and recovery.
02Live links to pages, campaigns and short links elsewhere in StackDeck, which open where you edit them.
03Built for the answer after the answer
Findset owns the workspace knowledge model. Next, Replydeck retrieves policies, troubleshooting steps, and product context from that one approved place.
Today, teams can structure, search, permission, version, and export the knowledge inside Findset.
The product direction is to let Replydeck retrieve approved knowledge through the Findset API and surface it where agents and customers need it.
From draft to trusted answer
Findset keeps comments, reviews, and history right beside the knowledge.
01
02
03
Findset for StackDeck
Start a knowledge space for the policies, decisions, files, and product context your team needs to find again.