Library connections: authorise and manage connected accounts
A named library connection lets an administrator authorise an external account once and lets service designers select it in compatible actions. Open Library settings → Integrations → Connections. Each environment has its own authorisation and status.
Check the available connection
Managed connections are hosted Govform QA pilots where enabled; their presence in the catalogue does not establish Production readiness or your account's access. Connection creation currently requires the relevant staff beta permission as well as library administration access. Manual authentication remains available for supported Connector revisions and ordinary API actions.
Google Drive and Google Sheets share a Google connection. Jira Cloud and Jira Data Center are different providers. Choose the provider/account required by the saved action rather than substituting a similarly named connection.
Create and authorise
- Create a connection with a meaningful name and the supported provider.
- Select an environment and only the offered permissions needed by the service.
- Select Connect, complete the provider's sign-in/consent and choose the required account or site.
- Return to Connections and check the environment's status and account identity.
- Select that connection in a compatible Connector or API action, save the service and deploy it to QA separately.
A draft can be saved before authorisation. Saving an action does not grant consent. Signing an AI client into Govform through MCP is also separate from authorising this external provider.
Connection settings reference
| Item | Meaning |
|---|---|
| Name and connection ID | The name helps designers choose. The existing connection's ID identifies it within this library; do not copy IDs between libraries. |
| Provider and revision | The selected provider definition. A Connector action must match the provider/revision required by its recipe. This is separate from the Connector's definition revision. |
| Environment | Separate QA/Staging/Production policy, authorisation and delivery status where supported. A successful QA connection does not authorise Production. |
| Requested permissions | The finite permissions selected in Govform. Provider-reported grants may differ; some providers report only the last request. |
| Account or site | The identity selected during consent. Use a new connection to select a different account/site. |
Reconnect or disconnect
Reconnect through the provider if consent expires or the connection asks for attention. Reconnect retains the same account binding; use a new connection for a different account. Reducing requested permissions does not prove an older grant was revoked.
Disconnect disables that environment's connection and distributes the change. Wait for the delivered status before treating it as complete. Revoking Govform at the provider is a separate operation available through the provider's access-management route. Review dependent services before either change.
Keep credentials out of service definitions
Managed access and refresh tokens are not entered into Form JSON, Properties, Secrets or action results. Provider application registration is operated by Govform for these managed connections; customer-owned custom OAuth apps are outside this release. For manual authentication, use the selected recipe's named Properties and Secrets instead.
See Connector action settings, API actions and the integration directory.