---
title: "Contribute to Y2"
description: "Publish a briefing, report a problem, or contribute an integration."
canonical: https://y2.dev/docs/community/contributing/
---

# Contribute to Y2

Publish a briefing, report a problem, or contribute an integration.

Choose the path for your contribution.

| Goal                             | Next step                                                |
| -------------------------------- | -------------------------------------------------------- |
| Publish a briefing               | [Share a profile](https://y2.dev/docs/profiles/sharing)  |
| Report a product or docs problem | Use app support or email <support@y2.dev>                |
| Report public content            | Send its profile URL and the specific concern to support |
| Build an integration             | Start with the [API guide](https://y2.dev/docs/api)      |
| Change an SDK or CLI             | Follow the contribution rules in that tool's repository  |

## Publish a community briefing

Review at least one generated report before sharing the profile. Remove private instructions, customer data, credentials, and confidential sources. Follow [Share a profile](https://y2.dev/docs/profiles/sharing), then inspect the result in **InfoOps → Discover**.

## Report a product or documentation problem

Use the support widget when available. Email support if the widget is hidden or unavailable. Include:

- The app route or docs URL.
- The active workspace plan, if relevant.
- The steps to reproduce the problem.
- The expected and actual results.
- Relevant timestamps, request IDs, error text, or screenshots.
- Whether the problem occurs every time.

For a docs correction, identify the inaccurate statement and provide evidence for the replacement.

Remove sensitive information

Do not send API keys, signing secrets, verification codes, payment details, or unredacted personal data. Remove authorization headers before attaching logs.

## Report a security concern privately

Email <support@y2.dev>. Include the affected feature, impact, reproduction steps, and a safe demonstration. Do not publish exploit details, credentials, or another workspace's data.

## Build an integration

Use the [OpenAPI contract](https://y2.dev/docs/api/openapi) and [authentication guide](https://y2.dev/docs/api/authentication). [Integration recipes](https://y2.dev/docs/api/integration-recipes) show common tasks. For notifications, follow [Webhook delivery](https://y2.dev/docs/delivery/webhooks).

Contact support before describing an integration as endorsed by Y2.

## Work on an SDK or CLI

Start with the [TypeScript](https://y2.dev/docs/sdks/typescript), [Python](https://y2.dev/docs/sdks/python), or [CLI](https://y2.dev/docs/sdks/cli) page. Open the linked repository. Read its contribution rules, tests, release process, and license.

Check the artifact's license

The platform and API contract use proprietary terms. Documentation, examples, and external SDKs can have different licenses. Check the specific artifact before using or changing it.

Keep changes focused. Validate examples against the current contract or app behavior. Update affected documentation and run the repository's relevant tests.
