Skip to content

Suggested searches

    Search all documentation ↑↓ to navigate Enter to open Esc to close

    UpCloud

    Connect UpCloud as an access review source using a main-account API token to review every account and subaccount on your UpCloud contract.

    Markdown

    Probo reads your UpCloud contract’s main account and its subaccounts through the UpCloud API so you can review who has access.

    • Probo organization administrator access
    • Access to the UpCloud main account (a subaccount only sees itself)
    Probo fieldUpCloud fieldNotes
    Namefirst_name, last_nameFrom account details. Falls back to username when the name is empty
    EmailemailFrom account details
    Roleroles.roleAny of technical, billing, aux_billing
    AdmintypeFlagged as an administrator for the main account (any type other than sub)
    StatusNot supported
    MFANot supported
    Last loginNot supported
    External IDusernameStable identifier used to track the account across reviews
    Created atNot supported

    The UpCloud Control Panel shows a 2FA status column under People, but the public API does not expose that field on any account endpoint, so Probo cannot collect it. The same applies to account status and last login.

    Creating an API token in the UpCloud Control Panel

    1. In the UpCloud Control Panel, signed in as the main account, go to Account > API tokens.
    2. Click Add new API token and enter a name (e.g. Probo Access Review).
    3. Set Expiration. It defaults to 30 days, and 365 days is the maximum. The source stops syncing once the token expires, so pick the longest period your policy allows and plan to rotate the token before that date.
    4. Leave Allow this token to create other tokens unchecked. Probo only reads accounts.
    5. For Probo Cloud, you can restrict the token to the egress IP for your region, or keep Allow access from all IP addresses checked. For a self-hosted deployment, restrict the token to that deployment’s fixed egress addresses.
    6. Click Create API token, then copy the token (ucat_…) and store it securely. It’s shown only once.
    1. In Probo, go to Settings > Connectors and click Add more to open the Marketplace.
    2. Find UpCloud and open it.
    3. Enter a Name for the connection (e.g. main), paste the token into API key, and click Connect.
    4. Go to Access Review > Sources, click Add sources, tick UpCloud, and click Add.

    Probo names the source after the account the token belongs to and pulls the contract’s accounts into your campaigns.

    • Token rejected. Confirm the token starts with ucat_ and has not expired. If you restricted the token to specific IPs, include the Cloud egress address for your region. A self-hosted deployment can use its own fixed egress addresses. Your UpCloud username and password won’t work here.
    • The contract’s accounts don’t come through. Account listing is only available to the main account, so a token created under a subaccount is refused and the source cannot enumerate the contract. Create the token while signed in as the main account.
    • An account is missing its name and email. The token couldn’t read that account’s details. The account still appears in the review under its username.