Engineering
Teaching Auno to read all your team’s docs
How we index what your team already wrote, and why Auno only sees what you can.
8 min read
Jonah Park
Co-founder & CTO
Auno is only as useful as the context it can reach. Most of that context already lives in your docs, wikis and threads, so teaching Auno to read them well was one of the first big problems we solved.
Indexing without copying everything
When you connect a tool, Auno builds a search index of the pages you choose. It stores what it needs to find the right passage quickly, and always links back to the original, so you can check its sources.
Permissions on every request
The hard part isn’t search, it’s access. Every time Auno looks something up for you, it checks your permissions in the source tool first. If you can’t open a page, Auno can’t use it in your answer.
Per person. Two teammates asking the same question can get different answers.
Always current. Remove access in the source tool and it’s gone from Auno too.
Auditable. Every answer shows exactly which pages it used.
What’s next
We’re working on faster syncing for very large workspaces, so new pages become searchable within seconds of being written.
Share this post
Written by Jonah Park
Co-founder & CTO at Auno. Jonah writes about the systems that let Auno understand your work.
