Per-customer API credentials for all integrations mapped to PSA company

Problem
Each integration currently accepts one connection. That works when an MSP has partner, multi-org or delegated access that covers every customer. It doesn’t work for customers on direct, customer-owned licensing, where only a single-org key is available. This is common for inherited contracts, customer-procured subscriptions, and customers who won’t move to partner billing.

Examples

Cisco Umbrella: a key created inside one customer’s organisation only works for agents not running on a ticket. On a ticket, Neo acts only in the Umbrella org mapped to that ticket’s company, so ticket-triggered agents can’t make Umbrella calls with a single-org key. The integration can’t support the main use case: agents working that customer’s tickets.
Mimecast: a single-client credential works for that client only, so we can connect just one direct-licensed Mimecast customer.

In both cases, restricting which agents can use the integration secures the one customer we connect, but it doesn’t scale beyond them.

Requested change
Allow multiple credentials per integration, each mapped to one or more PSA companies, using the same company mapping Neo already applies to MSP-level keys. This should be a platform-wide credential model rather than a per-integration fix, so new integrations inherit it.

Suggested behaviour

Add one or more credentials per integration, each with a label and a mapped PSA company.
On a ticket, Neo uses the credential mapped to the ticket’s company.
A per-company credential overrides the MSP-level key for that company, so partner-managed and direct-licensed customers can run side by side.
If no credential exists for the ticket’s company, the agent fails safely with a clear message and never falls back to another customer’s key.
Each credential shows its own connection test and health status.

Security benefit
Strict per-company scoping keeps one customer’s data out of another customer’s ticket. This is stronger isolation than relying on agent access restrictions alone.

Who this helps
Any MSP with a mixed estate of partner-managed and direct-licensed customers for the same product, which is most mid-market MSPs.