PROJECT HUB / 4 MINUTES
Connect the evidence
Let Seerist read your product’s story without handing it a paintbrush.
Your little win: Distinguish read-only repository knowledge, connected research and development access.
01 / SEE HOW IT FITS
The big picture, in little steps.
Choose the repository’s job
Connect application or marketing source using a dedicated GitHub App with read-only Contents and Metadata permissions. Enter the repository and App installation details in Seerist, not in this guide.
02 / YOUR TURN
Have a little go.
This is your practice table. Everything stays here—no account, real AI calls, or changes to Seerist.
Setting out the pencils…
03 / DO IT IN SEERIST
Ready for the real thing?
Before you start: A dedicated read-only GitHub App installed on the selected repository; an administrator for setup.
- 1
Choose the repository’s job
Connect application or marketing source using a dedicated GitHub App with read-only Contents and Metadata permissions. Enter the repository and App installation details in Seerist, not in this guide.
- 2
Verify and sync
Verify and connect read-only, then Sync changes. The initial index includes source paths and selected documentation. Use Read file for bounded on-demand reading.
- 3
Use grounded change notes
Repository snapshots retain commit identities. With workspace automation enabled, due checks can create change notices and release assessments. Committed source is not proof that a feature is deployed.
- 4
Add other research when needed
Project hub has a separate customer-connected Apify website-research path with explicit permission and per-run charge limits. Transcript and mailbox sources also need their own setup. They do not unlock restricted platform access.
A little thing to rememberRead-only knowledge never pushes code. Studio’s development connection is separate and can perform reviewed development/deployment operations.
Opens the real app in a new tab. Sign in and check the selected workspace before acting.
Take a little note with you.
About this lesson
Checked September 13, 2026 against app source a365066. Based on docs/connected-workspace.md. This is a source-based guide, not a claim that every provider action was live-tested.