Embedded actions and panels
An app bar adds an action button or an embedded iframe to a supported Caraer location. Record actions can receive record context; toolbar actions can serve tasks that do not depend on one selected record.
Why integrate
Section titled “Why integrate”Users can invoke your service from the relevant record or view. Your integration receives the available context, reducing the need to ask users to find and re-enter identifiers in another application.
What you could build
Section titled “What you could build”Add a document-generation button to a record, a dialog that collects an attachment before invoking a function, or an embedded panel showing information from your service beside a Caraer record.
Start integrating
Section titled “Start integrating”Choose a placement with App bars, then follow Collect input from an app-bar action. That guide explains the distinction between installation settings and values collected by an action dialog.
Available context depends on placement: a toolbar action may have no selected record. Embedded pages must validate their short-lived iframe session before trusting its context or scoped token. Installation visibility controls where an app bar appears; it does not replace the permissions required for its actions.