Global vs Project Apps
Why some apps work everywhere with one account while others need a specific resource linked per project.
Global apps: one account, every project
Some apps are global. You connect an account once and it works across all your PandaOS projects. Gmail is a good example: you have one inbox, and whether you are working on a frontend project or a marketing campaign, "check my email" means the same thing.
Global apps do not need any per-project configuration. Connect the account and the actions are available everywhere.
Project-scoped apps: one resource per project
Some services manage multiple distinct resources. You might have three Supabase databases, two Vercel projects, or five analytics properties. When you say "run this migration," PandaOS needs to know which database you mean.
Project-scoped apps solve this by letting you link each PandaOS project to a specific external resource. Your "Frontend" project links to your production Supabase database. Your "Admin Dashboard" project links to a different one. Once linked, every action automatically targets the right resource - no ambiguity, no risk of running a migration against the wrong database.
Currently, Supabase and Vercel are project-scoped. Both manage multiple independent resources where targeting the wrong one could have real consequences.
Linking a resource to a project
After connecting a project-scoped app's account, you link each PandaOS project to a specific resource. The settings show your PandaOS projects alongside the available external resources (databases, deployment targets, etc.), and you map each one.
When only one external resource exists, PandaOS selects it automatically. When you have several, you choose which resource each project should target.
Once saved, the link is persistent. Every action PandaOS takes through that app - queries, deployments, migrations - automatically targets the linked resource for whichever project you are working in.