Configuration
Settings & notifications
Set what Goosy flags and blocks, who gets notified, and who on your team can change it.
How settings apply
Settings come from three levels. The most specific one wins:
| Level | Where | What it covers |
|---|
| Organization | Organization settings | Defaults for every project. |
| Project | Project settings | Overrides the organization defaults for that project's repositories. A project override replaces the whole set of defaults, not single fields. |
| Repository | The project's Repositories page | Per repository: PR scan on or off, Deep Scan on or off, a severity threshold, and extra exclude paths. |
A project can only tighten two safety settings. If the organization sets Block merge on Critical findings, or alerts admins about them, a project can't turn either one off. Only Owners and Admins can change settings. Members see them read-only.
PR review settings
| Setting | Default | Effect |
|---|
| Minimum severity to comment | High | Lowest severity posted on pull requests. Lower findings are still recorded in the dashboard. |
| Suppress test & generated files | On | Skips findings in test and generated files. |
| Exclude paths | None | Glob patterns Goosy ignores in pull requests. |
| Block merge on Critical findings | Off | Fails the goosy/scan status when a critical finding is reported. |
| Re-scan on PR update | On | Reviews every new commit. When off, only the first version of each pull request is reviewed. |
Goosy also reviews pull requests from bots such as Dependabot. For what a review posts and how fixes work, see PR Review. For Deep Scan schedules, report size and exclusions, see Deep Scan settings.
Notifications
Goosy sends notifications by email.
Pull requests
| Setting | Default |
|---|
| Notify PR author when review starts | Off |
| Notify PR author by email (when the review finishes) | Off |
| Notify repo admins on Critical findings | Off |
Deep Scan
| Setting | Default |
|---|
| Report delivery | Email |
| Recipients | Organization admins, unless you list specific people |
| Notify on scan completion | On |
| Notify on scan start (scheduled scans only) | Off |
Workspace
| Setting | Default |
|---|
| Notify admins when someone joins | On |
| Send workspace health digest | Off (weekly when on) |
Team and roles
| Role | Can |
|---|
| Owner | Full control of the organization. |
| Admin | Manage settings, repositories and members, and invite people. Has access to every project. |
| Member | Works in the projects they've been given access to. Sees settings read-only. |
- Admins and Owners invite people by email. An invite expires after 7 days. Admins and Owners can resend or revoke pending invites.
- You can't grant a role higher than your own.
- Each member uses one seat. If your plan has no free seat, the invite waits for seat approval.
MCP access tokens
Create a personal token for your AI coding agent under
Settings → MCP Access Token. See
MCP server for setup.
