User guide
Learn to get the most out of WorkDigest in 5 minutes.
1. Create your account
Visit the sign-up page and fill in your name, email and password. You'll get instant access to the WorkDigest dashboard on the Free plan: 1 project, 2 connectors and 10 queries a day so you can try it with no commitment.
If your organization already has a team account, ask your admin for an invite instead of creating a new account.
2. Create your first project
From the dashboard, click "New project" and give it a descriptive name (e.g. "Website Redesign" or "Cloud Migration Q3"). A project groups all related information: tickets, emails, documents, meeting notes. It's the context WorkDigest will use to answer your questions.
Name your projects the way your team already names them day to day. WorkDigest is more useful the more specific the name is.
3. Connect your information sources
Inside a project, go to the "Connectors" section and add the sources your team uses:
Cloud sources
One-click OAuth: Google Drive, Gmail, Slack, GitLab cloud, GitHub, Confluence cloud, Outlook.
Internal sources
Require the local agent: Redmine, Jira Server, self-hosted GitLab, network files, on-premise SharePoint.
For internal sources, you need to install the WorkDigest local agent — a lightweight executable that connects from your PC or a server on your network. The agent reaches your internal tools and sends the data to WorkDigest securely, without the information leaving your infrastructure until it's indexed.
Start with a single connector to get familiar. You can add more at any time.
4. Ask in natural language
Once your sources are connected and your documents indexed, go to the chat and ask whatever you need in natural language. Examples:
- →“What's the status of the website redesign task?”
- →“Who approved the change in project scope?”
- →“How many hours have been logged on the project this month?”
- →“Summarize the latest changes in the GitLab repository”
WorkDigest will answer citing the exact sources with a relevance score. Every fact is traced back to its origin: a Redmine ticket, an email, a GitLab commit.
The more specific your question, the better the answer. "Project status" is useful, but "What tasks are blocked this week?" is more precise.
5. Next steps
Once you've got the basics down:
- •Add more connectors to broaden the project's knowledge base
- •Create more projects if you manage several initiatives at once
- •Upgrade your plan if you need more queries, more projects, or the 24/7 server agent
- •Share with your team by inviting other users from the project settings (Pro plan and above)
Have questions? Get in touch on the contact page.