Dispatch
CloudOpen 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.Manage billing
Open Billing to complete billing setup, review invoices and transactions, and manage billing access for the organization.Complete or upgrade 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: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:
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. To connect VCS integrations, open Settings > Integrations or see:Monitor operations
If you have access to operational views, use them to monitor activity across runs, deliveries, installations, queue health, connected Jira sites, organization usage, and organization limits.Operations dashboard
Open Operations Dashboard to view metrics and charts for runs and deliveries. Use it when you need an at-a-glance view of operational volume and outcomes before opening a specific run or delivery. Run charts support selectable windows of 10, 30, or 90 days.Deliveries
Open Deliveries to browse delivery events, filter the list, group or aggregate deliveries, and review daily delivery charts. Select a delivery to open its detail panel. Delivery details help you understand the delivery outcome and gates before the delivery created or updated run activity.Queue
Open Queue to view queue health, stuck runs, and lane backlog information. Use it to understand whether queued work is accumulating before opening individual runs for more detail.Installations
Open Installations to view and filter connected installations. Select an installation to open details such as its bot identity, connected repositories, status, and usage. If your role allows editing operational limits, select an installation and use the Installation detail panel to edit its run cap. For setup tasks, use Settings > Integrations or the integration-specific pages instead:Organizations and caps
Open Organizations in the operational views to inspect organizations and per-organization usage. Select an organization to open usage charts and concurrency information. If your role allows editing operational limits, use the organization caps editor to adjust daily or concurrent run caps.Jira connections
Use the Jira connections list to view connected Jira sites for the organization. Select a Jira connection to view token and webhook expiration details and related metadata. For setup and disconnection steps, see Set up Jira.GitLab service accounts and GitLab API usage
Open GitLab Service Accounts to list service accounts and inspect their access. Select a service account to view personal access token expiration details and related information. Open GitLab API Usage to review daily charts and per-service-account usage. Usage volume categories are ok, error, and rateLimited. The view can also support sorting and filtering usage.Feature flags
Open Feature Flags to list flags and manage their state in the Feature Flag editor. Feature flag states are unset, on, and off.Egress policies
Open Egress to review egress policies and their allowed hosts. Use this view to confirm which hosts are allowed by policy.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
- Staff or non-staff activity, when that filter is available to your role
- Time range, including 24 hours, 7 days, and 30 days
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, and capped log excerpts. 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.
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:completedfailedcanceled
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 Settings > Workflows 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.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.Search and navigate quickly
Use console search to find operational resources. If the command palette is available, use it to navigate quickly to specific runs or deliveries.View usage
Open Usage to review token and compute usage across organization runs. Usage can be grouped by model, workflow, or model integration, and bucketed by day or month. By default, Usage groups data by model and uses the day bucket. Usage charts aggregate recorded usage for your organization over the selected range. The usage view supports these time ranges:- 7 days
- 30 days
- 90 days
- all time