When a customer needs to be disconnected from an integration made with Makini, there are two options: deactivating or deleting it. They have different effects, so it's important to choose the right one.
Deactivating a connection pauses it:
The connection also continues to consume credits from your account.
Deleting a connection removes it entirely:
The credits that connection was using are released back to your account.
In both cases, any workflows you've configured in Makini remain intact: they are not tied to the connection itself.
Use deactivation when there's a chance the customer may reconnect in near future. Because all settings and mappings are preserved, reactivating the connection is straightforward with no reconfiguration needed. Keep in mind the connection will continue to use credits during this time.
Use deletion when the customer's contract has ended and Makini should no longer have access to their system. This is the appropriate option from a compliance standpoint: it ensures Makini is fully de-authenticated and customer data is deleted at the connection level.
All disconnection requests must be submitted through a Zendesk support ticket at https://makini-brightly.zendesk.com/hc/en-us/requests/new. Select either "Deactivate connection" or "Delete connection" as the ticket type.
Include the customer name and the required date for the action (the date you want the connection paused or deleted, it is a required field). Makini will process it per the SLA in your contract and close the ticket once complete. You'll receive a confirmation notification when it's done.
Migration connections are disconnected automatically by Makini. The workflow is:
No request from the Brightly PM is required. The automatic workflow ensures credits do not sit idle after the migration is delivered.
If a migration connection needs to be kept active beyond 30 days for a documented reason, the PM can request an extension through the same Zendesk ticket before the disconnection date.