What to connect
Choose the first work area that already contains useful company context.
Setup
Start Pantasso by answering one real company question.
Pantasso setup is about trust: what may it read, what should stay private, which question should it answer first, and which assistant should use that context. You do not need to understand the technical platform to make those decisions across the available integrations.
Why setup matters
Setup teaches Pantasso what your assistants may trust.
Pantasso is useful when it can answer from approved company sources and show where the answer came from. Setup defines the first source, the private areas, the first question, and the assistant boundaries.
What to keep private
Name excluded channels, folders, chats, or files before syncing anything.
What value to expect
Look for one answer with sources, one brief, one assistant check, and clear next actions.
Common small-company setup
Pantasso should fit the tools the team already uses.
A normal first workspace might have Obsidian notes, Google Drive, Slack, local docs, GitHub, CRM records, spreadsheets, deployment data, existing AI agents on a server, and a website. Pantasso does not replace those tools. It gives the team and its assistants one trusted place to look across the approved parts.
Obsidian vault
Treat the vault as local Markdown files. Start with one project folder or a small set of current notes, not the whole history.
Google Drive
Choose one folder with the plans, specs, or meeting notes people already trust.
Slack
Choose the channel where decisions, requests, and handoffs are most likely to appear.
GitHub
Choose one active repository when issues, pull requests, and comments explain current work.
Business systems
Add integrations for project systems, CRM records, deployment events, spreadsheets, databases, and structured imports once the first answer proves value.
Local computer docs
Upload approved Markdown, text, or JSON files when credentials are not ready or the useful context is already exported.
Existing AI agents
Keep agents running where they already run. Give them one rule after the first answer works: check Pantasso before answering company-specific questions.
Company website
Keep the website separate at first. After Pantasso can answer with sources, the site can use approved context for public pages, support, or handoff workflows.
Plan the first source with us.
A focused evaluation should prove value first: choose one approved source, ask one real question, review the evidence, then decide where Pantasso should help next.
Step by step
The first Pantasso workspace should be useful the same day.
1
Open the source selector
Choose one owner and the first place Pantasso should look. Start narrow: one channel, one folder, one repository, one CRM/project target, one table, one chat, or one small file set is enough.
2
Choose what Pantasso may see
Use plain source choices to mark what is approved for launch and what should stay private. This keeps setup comfortable and avoids pulling in material the team did not intend to share.
3
Create the Pantasso workspace
Pantasso creates the workspace and checklist. The team does not need to learn commands to make the important decisions.
4
Check access before anything is brought in
Pantasso confirms that the selected sources can be reached and clearly lists anything that still needs attention.
5
Bring in a small first set
Add a small set of approved information, then review what Pantasso saw, what it skipped, and what is ready to search.
6
Ask real work questions
Use questions the team actually cares about: what changed this week, what decisions were made, where the latest plan is, or what is still open. Pantasso should answer with sources or explain what approved context is missing.
7
Invite assistants with clear boundaries
Give each assistant a name, a role, the sources it may use, where it should save work, and a simple rule: check Pantasso before answering company-specific questions.
8
Finish with a simple handoff
Review the short workspace brief, confirm the backup, and export a redacted support report so Pantasso can help quickly later.
Pick your first source
Start where the most useful answer already lives.
The first source should be small enough to review and important enough to answer a real question. You can add the rest of the directory after the first win.
Obsidian or local docs
Choose this first when the company already has useful Markdown notes, exported docs, specs, or meeting notes on a computer.
Start with: Choose the Files card, then upload one approved project folder or a small set of Markdown/text files.
Slack
Choose this first when decisions, handoffs, and requests happen in channels.
Start with: Choose the Slack card, then use the simplest approved channel choice and include threads.
Google Drive and Docs
Choose this first when plans, specs, notes, or policies are the source of truth.
Start with: Choose the Drive card, then pick one active folder, not the whole drive.
Project, CRM, or deployment system
Choose this first when work state lives in issues, tickets, CRM records, deployment events, or project databases.
Start with: Choose the matching integration, then pick one active repository, project, pipeline, or record scope.
GitHub
Choose this first when project state lives in issues, pull requests, and repo discussions.
Start with: Choose the GitHub card, then pick one active repository and the work types to include.
Telegram
Choose this first when operating or external conversations happen there.
Start with: Choose the Telegram card, then pick one approved chat and a recent date window.
Files
Choose this first when credentials are not ready or you have a small approved export.
Start with: Upload a few text, Markdown, or JSON files for one current project.
What good setup looks like
Small scope, real questions, clear handoff.
Approved sources
The team can see which approved messaging, Google Workspace, Microsoft 365, email, calendars, spreadsheets, admin directories, code and project systems, CRM, finance, commerce, support, observability, cloud audit, files, databases, webhooks, SDKs, and structured imports sources are included.
Trustworthy answers
A question returns source-backed context, or Pantasso plainly says which approved source is missing.
Agent profiles
Assistant profiles say what each assistant may read, what it may draft, and when it must ask a human.
Easy support
The redacted support report explains workspace health, source setup, useful context, and the next recommended action.
Day-one outcome
You should know whether Pantasso is useful after the first session.
1
One approved source is connected or clearly marked as needing access.
2
One real question returns source-backed context or a plain gap report.
3
The operating brief shows open items, decisions, source freshness, and next actions.
4
One assistant profile is saved and smoke-tested.
5
Private or excluded areas are written down before more sources are added.
6