Settings
Maintain workspace identity, key policies, and integration settings without changing payment truth.
On this page
Before changing a setting
Settings apply to the merchant and environment you are viewing. Check the merchant name, environment, and your permissions before saving. Authorized operators should confirm their selected client in /admin; merchant users make changes within /dashboard.
- Identify which backend service or teammate depends on the setting.
- Record the intended change, owner, and a rollback or recovery path.
- Test changes to scopes, mappings, or webhook delivery in a non-production context first.
- Review available audit or activity records after saving.
Workspace and integration settings
| Area | Review | Boundary |
|---|---|---|
| Workspace identity | Merchant name and operational contacts. | A name change does not move records into another organization. |
| Access policy | Who can manage team members, integrations, and keys; which API scopes may be issued. | Changing a policy can affect services; review existing key behavior explicitly. |
| QuickBooks | Company identity, environment, connection state, and sync information. | Consent, sync completion, and invoice data quality are separate. |
| Stripe integration | Carden keys, report activity, and supported configuration. | Stripe credentials remain in your backend; Carden has no Stripe OAuth setup. |
| Outbound webhooks | Destination, event subscriptions, signing secret, and delivery status where exposed. | An outbound Carden event is not a verified Stripe provider event. |
Rotate a Carden key
- Create a replacement key for the same intended integration and environment, with only the required scopes.
- Store it in your secret manager and deploy it to the relevant backend or worker.
- Verify new requests and report delivery. Check older outbox work uses the replacement credential without changing event IDs.
- Revoke the old key after successful cutover. If the old key may be compromised, prioritize revocation and follow your incident process.
- Confirm that revoked credentials no longer succeed and review recent usage for unexpected activity.
Keep report identity separate from credentials: rotating a key should not create new event IDs for already-persisted events. A retry remains the same event even when delivered by a replacement key in the same context.
Protect financial correctness
Configuration cannot make an unsupported invoice fact true. A mapping should preserve source meaning, and tax or shipping normalization must reconcile to the authoritative amounts. Changes to mappings should be tested against representative invoices and tracked with the source versions used.