PD DigitalOcean App Platform creates customer apps in your own DigitalOcean account. Save the provider token separately from the package that describes the app hosting you sell.

Prepare the intended account

Ask the DigitalOcean administrator to prepare a token authorised for the app operations you intend to offer, with account reads and any project access used for grouping. The module documentation describes Full Access and a narrower custom-scope alternative. A read-only token can pass the account check while refusing app creation or changes; passing that check is not proof of write permissions.

DigitalOcean documents its API token scopes. Have the administrator review the specific permission named by an error rather than replacing every restricted token with broader access automatically. Record the chosen expiry in your normal maintenance process.

Save the connection

1. Open Settings → Company → Modules.
2. Find PD DigitalOcean App Platform under Installed and choose Manage.
3. Add a recognisable account name and enter the prepared token in API token, then choose Save account.
4. Open PD Modules → DigitalOcean App Platform and run Test Connection. Select the intended account when creating the package.

A later edit with an empty token field keeps the saved token; it does not clear the connection.

Interpret the account check

The module’s Test Connection button checks every active connected account for this module and names accounts that fail. Each check reads the DigitalOcean account; it does not create an app, deploy code or verify every resource permission. Use the module-wide result to identify a failed saved account, then review that account rather than replacing every token.

For an authentication error, confirm the intended saved account and whether its token is wrong, expired or revoked. For a permission error on a particular operation, review that operation’s required scope. For a reachability error, check the host’s outbound HTTPS access to DigitalOcean. Do not repeatedly create apps to diagnose authentication.

When replacing a token, save and verify the intended replacement before the administrator retires the working one. An account-read success alone is not proof that all management operations work with a narrower replacement.

Do not send the token, account credentials or customer records.

See the PD DigitalOcean App Platform Blesta guide for related setup, or explore PD DigitalOcean App Platform.