Button Transfer

Type: Explanation | Audience: OneClick admins | Goal: Understand how interface data behaves when a button is transferred between organizations

A button transfer copies a OneClick button — including all its interfaces, views, and interface variables — from one organization to another. The target admin must first issue a transfer-enabled API key; the source admin then uses it from the button's Transfer tab. The original button stays untouched in the source organization.

For security, confidential interface variables and request headers are stripped in transit. The target admin has to re-enter those secrets before the copied button works.

Full configuration steps, validation rules, audit logs, and rate limits live in the OneClick admin guide: Button transfer →.