Skip to content

Open-source manufacturing ERP, MES and QMS. Quoting, MRP, inventory, shop floor, quality and lot/serial traceability on one Postgres schema, with a REST API and MCP server. Self-host or use Carbon Cloud.

chore(docs): regenerate the agent knowledge base

aashucef1343274e1
diff --git a/apps/erp/app/modules/agent/kb/docs/integrations/project-management.md b/apps/erp/app/modules/agent/kb/docs/integrations/project-management.md
index c3fca675b0..5c16fa90b4 100644
--- a/apps/erp/app/modules/agent/kb/docs/integrations/project-management.md
+++ b/apps/erp/app/modules/agent/kb/docs/integrations/project-management.md
@@ -11,6 +11,19 @@ to an external issue and keep the two in step, status, assignee, and notes sync
Authenticate with a **Linear API key** (it begins with `lin_api`).
+ ### Create the webhook in Linear
+
+ In Linear's API settings, create a new webhook and paste the URL shown in Carbon's setup instructions
+ (`/api/webhook/linear/<your company id>`). This is how changes made in Linear reach Carbon.
+
+
+ ### Copy the signing secret
+
+ Linear shows a **signing secret** on the webhook's detail page. Paste it into **Webhook Signing Secret**.
+ With it saved, Carbon only accepts webhook requests Linear has signed, and rejects any that are more
+ than a minute old.
+
+
### Paste your Linear API key
Provide your Linear API key. Carbon checks the `lin_api` prefix.
@@ -24,15 +37,28 @@ Authenticate with a **Linear API key** (it begins with `lin_api`).
| Setting | What it controls |
| --- | --- |
| API key | Your Linear API key — Carbon checks the `lin_api` prefix. |
+| Webhook signing secret | Optional. When set, webhook requests without a valid Linear signature are rejected. |
+
+A Linear or Jira webhook with no secret saved in Carbon still works, so older setups keep syncing, but
+Carbon cannot tell its requests from forged ones. Add the secret to every webhook you create.
## Jira
-Connect over **OAuth**. There are no fields to fill in beyond authorizing Carbon.
+Connect over **OAuth**. The only setting is an optional webhook secret.
### Authorize over OAuth
- Authorize Carbon in Jira. There are no fields to fill in.
+ Authorize Carbon in Jira.
+
+
+ ### Create the webhook in Jira (optional)
+
+ For changes made in Jira to reach Carbon straight away, go to **System → WebHooks** in Jira and create a
+ webhook with the URL shown in Carbon's setup instructions (`/api/webhook/jira/<your company id>`),
+ subscribed to **Issue updated** and **Issue deleted**. Fill in the webhook's **Secret** field, and paste
+ the same value into **Webhook Secret** in Carbon. With it saved, Carbon only accepts webhook requests
+ Jira has signed.
### Link an action task
@@ -40,6 +66,10 @@ Connect over **OAuth**. There are no fields to fill in beyond authorizing Carbon
Once connected, you can link a nonconformance action task to a Jira issue, and status, assignee, and notes stay aligned in both directions.
+| Setting | What it controls |
+| --- | --- |
+| Webhook secret | Optional. When set, webhook requests without a valid Jira signature are rejected. |
+
Jira only appears when its OAuth client is configured server-side (`JIRA_CLIENT_ID`) — see
`docs/platform/self-hosting/environment-variables`.