Capabilities
Capabilities are optional actions that an extension app can implement to provide features in addition to the base functionality of an extension’s required actions. For example, the file output cloud storage extension has one required action: Write File, which writes a file to cloud storage. The extension also supports capabilities. One is List Directory Contents, which returns a list of folders on the cloud storage system to allow selection of a destination for the Write File action.
Define a capability in the app manifest
If you register an extension app using an app manifest file, you define capabilities within the manifest file actions object. An example capability definition, including the URL of the endpoint to call when the capability is invoked, is shown here. See Action schema for details about the properties.
In addition to defining each capability in the actions object, the manifest file must reference the capabilities in the extensions.actionReferences and extensions.capabilities arrays. See Extension schema for details.
Update capability settings in a form
When registering an extension app using a form, you can update each capability’s settings on the extension app’s integration details page.
During the form-based extension app registration process, if you select a file IO extension, its required actions are automatically added to the app. You can then configure the actions’ endpoint URIs and other properties on the Integration Details page. The extension’s optional capabilities can be added or removed only by editing the app manifest file. After you’ve added capabilities via the manifest file, you can edit them on the Integration Details page. See Action schema for information about action and capability properties in the app manifest file.

Shared capabilities
An extension app can include multiple extensions. If more than one extension supports the same action or capability, that action or capability can be defined only once for the app, and the extensions will share its definition. For example, if an extension app includes both the file input cloud storage and file output cloud storage extensions, the app can have only one definition for the List Directory Contents action, and both extensions will use that definition. Docusign does not support multiple versions of the same action or capability in the same extension app.
Next steps
- Get details about the app manifest schema for actions and capabilities.
- Learn more about connections.
- See sample app manifest files for all supported extensions.