Send a correction

​

The three kinds

​

What you get

{
	"id": "cmt0a1b2c3d4e5f6g7h8",
	"status": "received",
	"targetLabel": "Feature",
	"targetKey": "feat-workspace-cmek",
	"targetName": "Customer-managed encryption keys"
}

​

What makes a submission worth reading

​

Submissions are immutable

​

How to use it

Our data residency page proves EU-only storage. Send it as evidence on that feature.

​

Troubleshooting

• builder-identity-required — your account has no active builder identity. Claim access at sovrnti.io/builders.
• insufficient-scope — revoke the connection and reconnect; the authorization flow will re-request Builder.Write.Self.
• builder-target-out-of-scope — the name you gave resolves outside your own vendor.
• builder-requires-user-token — you connected with a machine token. Builder tools are personal (R-04); reconnect as yourself.
• builder-target-ambiguous — the name matched more than one thing. The error lists the candidates; pick one and resend.
• builder-target-needs-product — name a product before a group or a feature.
• builder-target-needs-group — name a group before a capability.
• builder-field-not-correctable — that field is not in the table above. Groups and capabilities have no correctable fields. A correction there is a taxonomy argument. Send it on the product with field: "description", and it is read as a flag.

​

See also

• Review your profile — call this first.
• Your submissions — what happened to it.
• For builders — what the four statuses mean.