CopyClipboardChar

The widget wraps the standard char display and appends a small button. Clicking it copies the exact stored value to the clipboard and flips the label to Copied for a moment. That is the entire job, and core uses it everywhere a human needs to move a value into another tool without typos: portal invitation links, TOTP secrets in auth_totp, livechat embed snippets, survey share URLs, calendar feed addresses.

It is also a small curiosity of the codebase: along with its two siblings it is registered under a CamelCase name, CopyClipboardChar, where nearly every other widget in the registry is snake_case. The registry is a plain case sensitive map, so the capitalization is part of the API.

Copy buttons are about error elimination, not convenience. Any value your team relays into email, chat or another system by selecting text will eventually be relayed with a missing character: an API key that fails, a payment reference that does not reconcile, a tracking link that 404s. A copy button reduces that class of support ticket to zero for the cost of one widget attribute.

The places it pays for itself fastest are customer facing values, credentials, and references consumed by other software: contract numbers quoted in bank transfers, webhook URLs pasted into third party dashboards, license keys sent to customers. If a value's only purpose is to be pasted somewhere else, it should carry this widget, and values that must not leave the screen on certain records can disable the button per record with the disabled expression.

Odoo Studio (Enterprise) has a first class path for this widget.

1. Open the form in Studio.

2. Drag a Text field onto the form, or select an existing text field.

3. In Properties, set Widget to Copy to Clipboard.

4. Optionally set Readonly. Most copy targets are computed or system generated values, and locking them makes the field a pure handoff point.

The same widget entry appears for Multiline Text fields in Studio's list, and the button copies the full stored value either way.

Studio stops at attaching the widget. The two refinements it cannot reach both live on the field node in XML:

Relabeling the button takes the string attribute. Setting string="Copy link" renames the button, since the widget uses the field's label text as the button caption.

Disabling the button conditionally takes the disabled attribute with a Python expression, evaluated against the record. Studio's conditional tools cover field visibility, not this button state.

Both are one line view changes, the kind of thing bundled into any Odoo customization pass rather than billed on its own.

Standard copy field

<field name="access_token" widget="CopyClipboardChar" readonly="1"/>

Custom button label

<field name="share_url"
       widget="CopyClipboardURL"
       string="Copy link"/>

Disable copying until the record is confirmed

<field name="payment_reference"
       widget="CopyClipboardChar"
       disabled="state != 'confirmed'"/>

Button only, value hidden

<field name="api_secret"
       widget="CopyClipboardButton"
       options="{'btn_class': 'secondary'}"/>

The Button variant renders no value at all, only the button, which is the right shape for secrets that should be transferable but never displayed.

The 19.0 source file defines one base component and three registered widgets, and knowing which is which saves guesswork:

CopyClipboardChar composes the standard char field plus the copy button with a clipboard icon. Declared supportedTypes is char only.

CopyClipboardURL composes the URL field instead, so the value renders as a clickable link with a link icon on the button. The clipboard still receives the raw stored value.

CopyClipboardButton renders only the button. It declares no supported types, and its one option, btn_class, feeds the Bootstrap button class with a default of primary. That option is new in 19.0.

Shared machinery worth knowing: the button label falls back to Copy unless the string attribute overrides it, the success state briefly shows Copied, and the disabled attribute is re-evaluated per record against the record's context, including unsaved values. The copy itself goes through the browser clipboard API, which browsers only expose in secure contexts, so an Odoo instance served over plain HTTP on a LAN will render the button but the copy can fail. Modules also ship their own derivatives, such as hr_recruitment's variant for interview links, so the trio here is the core surface, not the whole family.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. These notes come from the public development branch, which remains unstable until feature freeze, and this page is re-verified after release.

The button restyles from a boxed button to an inline link. The class string moves from btn-sm to btn-link btn-link-inline, so the copy affordance sits flush with the value instead of standing beside it as a bordered button. Screenshots in internal documentation will age accordingly.

The icons leave FontAwesome. Both the clipboard icon and the URL variant's link icon are replaced by the assignment glyph from the new icon set, part of the same iconography migration we have tracked across other widgets on the development branch.

No functional changes are visible: registry names, attributes and the disabled expression all carry over.