Use the Upsun Dispatch console

Manage organizations, billing, repositories, workflow settings, runs, notifications, and usage from the Upsun Dispatch web console.

The Upsun Dispatch console is the browser interface for day-to-day work in Upsun Dispatch. Use it to manage your organization, billing setup, connected repositories, workflow behavior, runs, notifications, and usage.

Some console sections are available only when your role has access to those views.

Open an organization

After signing in, open Organizations and choose the organization you want to manage. Organization pages are scoped to the selected organization, so repositories, workflow settings, runs, and usage shown in the console belong to that organization.

If you create a new organization, you become its owner. Owners and admins can update organization settings and manage access.

To manage organization details, open Settings > General. Owners can also use Delete organization from Settings > General and follow the confirmation flow when an organization should be removed.

Manage members and invitations

Open Settings > Members and roles to manage people and access.

Use Members and roles to review current organization members, change roles, or remove members. Upsun Dispatch supports the owner, admin, and member roles.

Use invitations to add new organization members by email address and role. You can invite a single recipient or multiple recipients in bulk, then resend or revoke pending invitations when those actions are available. Recipients accept an invitation by opening the link in the invitation email.

If pending invitations addressed to you are shown after you sign in, review the organization and role before accepting the invitation.

Manage billing

Open Billing to complete billing setup, review invoices and transactions, and manage billing access for the organization.

The free option includes a limited number of agent-minutes. When you need more, your organization can buy credits through the credit-purchase system or get paid access through an agreement with Upsun. If you move to the credit-purchase system, you can optionally enable Auto Top-Up so credit is always available. Moving to the credit-purchase system is one-way, so you cannot switch back to the free option afterward.

Organizations that pay for Upsun Dispatch, including by buying credits or via an agreement with Upsun, can open support tickets. For support eligibility and the support portal link, see Support for Upsun Dispatch.

Complete, upgrade, or link billing setup

Use the Billing Setup Wizard to set up billing, upgrade billing, or link an organization to an existing billing profile. Depending on the mode, the wizard can guide you through these actions:

Action	What you do
Select a billing account	Choose the billing account to use for Upsun Dispatch billing.
Select or create a billing profile	Choose the billing profile, or enter billing profile details.
Add a payment method	Enter the payment method required for credit purchases.
Purchase credits	Add credits for Upsun Dispatch usage.
Attach an organization	Connect the organization to the selected billing profile.

Add a payment method

Use Billing to add the payment method used for manual credit purchases and Auto Top-Up. Before saving payment details, confirm that the billing profile shown in Billing is the one you want to charge.

If you manage multiple organizations or billing profiles, check the selected organization before adding or updating a payment method.

Purchase credits

After a billing profile and payment method are ready, use Billing to buy credits for Upsun Dispatch usage. Review the selected billing profile, payment method, and credit purchase details before confirming the purchase.

Credit purchases add credit to the billing profile attached to the organization.

Manage Auto Top-Up

Auto Top-Up keeps credit available by purchasing additional credits according to the settings you configure in Billing.

Use Billing to enable Auto Top-Up, update its settings, or disable it when you no longer want automatic credit purchases. When Auto Top-Up is disabled, purchase credits manually from Billing when more credit is needed.

Manage billing users

Billing users are managed separately from organization members. Use the billing user forms to invite one or more email addresses, then assign each billing user one of these permissions:

Permission	Access
manage	Can manage billing users and billing details.
view	Can view billing information.

Use the edit billing user form to change a billing user’s permission when their billing access needs to change.

Review invoices and transactions

Use the billing area to review invoices and transaction history. Invoice details can include formatted invoice dates and billing periods. Transactions are grouped with descriptions so you can understand credit purchases, usage, and other billing events shown in the console.

Browse repositories

Open Repositories to view repositories available through your organization’s connected VCS integrations.

The repository list can be searched and filtered by integration. It can also show recent run activity when the console requests activity for a recent time window.

From the list, select a repository to open its detail page. The repository detail page includes repository-specific run activity, workflow controls, and security information.

To connect VCS integrations, open Settings > Integrations or see:

• Set up GitHub
• Set up GitLab

Manage verified repository accounts

Use verified repository accounts when your organization needs to prove control of a repository account. From the verified repository accounts card, you can request a verification code, confirm the claim after the code is in place, and remove a verified account that is no longer needed.

View repository security

Open Repositories, select a repository, then open Security to review CVE scan results for that repository.

The Security view shows the latest CVE scan state, recent findings, and the Accepted in osv-scanner.toml block for the selected repository. Findings are scoped to that repository. To learn how CVE scan runs work, see CVE scan.

Use Daily scan on Repository > Workflows > CVE scan to control scheduled CVE scans for that repository. When Daily scan is on, Upsun Dispatch runs the CVE scan workflow for the repository on a daily schedule and updates the repository’s security results. When Daily scan is off, scheduled daily CVE scans do not run for that repository.

To start a scan outside the daily schedule, open Repository > Workflows > CVE scan and select Run scan now.

View workflow runs

Open Runs to monitor workflow activity for the organization. Runs are shown newest first.

The runs list can be searched and filtered by:

• Status
• Event type
• Workflow
• Source, including GitHub and GitLab
• Time range, including 24 hours, 7 days, and 30 days

Run statuses include:

Status	Meaning
queued	Upsun Dispatch accepted the run and is waiting to start work.
running	Upsun Dispatch is actively processing the run.
completed	The run finished successfully.
failed	The run ended because a step failed or Upsun Dispatch could not complete the requested work.
skipped	Upsun Dispatch ended the run without further work because there was nothing applicable to do.
canceled	The run stopped before completion, such as because the associated pull or merge request was closed, because a supported Code review cancel comment stopped the active review, or, for an Issue to code run before a pull or merge request exists, because the source issue or ticket was closed.

A run can come from an automatic integration event, a manual trigger, or a manual comment command on GitHub or GitLab, depending on your workflow settings and integration.

Manual triggers and comment commands are subject to your organization’s access and integration permissions.

For how workflows start, see Workflows in Upsun Dispatch. For supported commands on each integration and review behavior, see Code review.

Open run details

Select a run to open its detail page. Run detail includes the run summary, status, duration, step statuses, timeline events, usage information, findings, plan diffs, live activity updates, and capped log excerpts.

When a run is for the CVE scan workflow, run detail shows the scan findings from that run. The latest repository-level CVE results are also available from the repository Security view.

When a Jira-triggered Issue to code run includes a plan approval gate, run detail also shows who approved the plan and the plan revisions that occurred within the run.

From run detail, you can:

• Check the current run status and duration.
• Review step-level progress and attempts.
• Inspect timeline events and the activity feed assembled from job logs.
• View prompts, tool calls, findings, artifacts, opened pull or merge requests, and push outcomes when the run produced them.
• View usage associated with the run.
• Open the related source entity display, when one is available.
• Re-run eligible finished runs.

The activity feed can include streamed job-log activity, step durations, prompts, tool calls, findings, and artifacts.

Follow logs

Run detail includes capped log excerpts. For complete or live logs, open the logs for a specific job or step attempt.

Live log following streams entries until the job reaches a terminal state. Run status updates and log updates are separate, so a run can show status changes while logs are followed from the job log view.

Re-run a run

You can re-run a run after it reaches one of these terminal states:

• completed
• failed
• canceled

A re-run starts new work from the original trigger and leaves the original run unchanged. Re-runs are accepted asynchronously, so the new run may still be held or suppressed by current workflow routing or gating.

Search and navigate quickly

Use console search to find runs.

Review approvals

Open Approvals to review runs that are waiting for a plan decision or have plan revisions to inspect. Select the pending item, review the plan or revision details, then approve or reject the plan from the available decision controls.

For Jira-triggered Issue to code runs, the plan approval behavior also depends on the plan approval setting. For the trigger phrases and Jira plan approval flow, see Issue to code.

View the related entity

When a run is associated with a source entity, such as a pull request or merge request, the console can show the current entity display. This can include the entity title, lifecycle state, review decision, head SHA, and related decisions.

If a run has no associated entity, the entity view is not available.

Configure workflow settings

Open Workflows from the top-level menu to adjust organization-level workflow behavior.

Use Workflows to change supported settings, including trigger mode, summary mode, GitLab fork-author admission, plan approval, model integration selection, quality, and repository overrides. Not every setting applies to every workflow.

For what these settings control, see Workflow settings. For Code review summary behavior, see Summary behavior. For stored model keys and defaults, open Settings > AI model keys or see AI models.

Turning summary mode off stops future summary content. It does not delete summaries that were already published.

Set repository overrides

Repository overrides let you pin workflow settings for a specific connected repository instead of using the organization default.

Use an override when one repository needs different trigger, summary, plan approval, or model integration behavior than the rest of the organization. If you no longer need the override, remove it to restore inheritance from the organization setting.

For details about what each workflow does, see Built-in workflows.

View notifications

Use the Notifications bell in the navbar to open the notification center. The bell is available from your account page and organization pages, and it can show your unread count.

In the notification center, you can page through notifications, mark individual notifications as read, mark all notifications as read, and dismiss notifications.

You can dismiss notifications you no longer need. Some notification types may clear over time.

When you click a browser push notification, Upsun Dispatch opens or focuses the app. If the notification references a run, Upsun Dispatch opens that run’s review in Approvals. If the notification does not reference a run, Upsun Dispatch opens or focuses the app home view.

View usage

Open Usage to review usage and cost reporting across organization runs. Usage reports can include run charts, model usage, agent time, workflow trends, token volume, compute usage, and currency or cost summaries.

Usage can be grouped by provider, model, workflow, or repository. By default, Usage groups data by model.

The usage view supports time ranges of 1 day, 7 days, 30 days, 90 days, or all time. The default range is 7 days.

Usage charts aggregate recorded usage for your organization over the selected range.

Open the GitLab section of Usage to review how much of each GitLab service account’s rate-limit budget is used over the selected range.

Install Upsun Dispatch as an app

If your browser offers an install option, you can install Upsun Dispatch as a standalone Progressive Web App. The installed app opens Upsun Dispatch in its own window and uses the same sign-in flow as the browser console.

Copy links safely

Run IDs are opaque, so avoid building run links by hand. To avoid encoding issues, copy links generated by the Upsun Dispatch console or from your browser’s address bar after opening the run detail page.