Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Understanding users and teamsUnderstanding role-based access controlManage usersManage teamsConfigure role-based access controlRBAC permissions reference
Understanding authentication in CloudBees UnifySet up multifactor authenticationConfigure SAML single sign-onConfigure OIDC authenticationConfigure network security policiesNetwork security reference
Understanding platform configurationUnderstanding environmentsManage properties and secretsManage environmentsTrack environment inventoryConfigure containersSet up preconfigured actionsConfigure notificationsSet up Slack webhook notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding CI workflowsUnderstanding custom actionsCreate a build workflowCreate a custom actionCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
View pending approval tasks in your inboxMonitor workflow runsView test results in runsView evidence in runsView deployments in runsManage workflow artifactsPublish test resultsPublish evidence itemsGenerate a software bill of materialsManage ServiceNow change requests
Configure workflow credentialsConfigure AWS credentialsConfigure container registry credentialsConfigure Git credentialsIntegrate CyberArk Conjur secrets
Understanding GitHub Actions integrationSet up GitHub Actions integrationDisplay GitHub Actions workflows and runsRegister GHA build artifactsPublish GHA deployed artifactsPublish GHA test resultsPublish GHA evidence itemsTrigger CloudBees workflows from GitHub ActionsScan with GitHub Actions
Understanding CloudBees CI and Jenkins® integrationConnect CI and Jenkins controllersMonitor CI and Jenkins buildsRegister CI build artifactsRegister CI deployed artifactsPublish CI test resultsConfigure CI security scanningCI and Jenkins integration reference
Build and publish container imagesUnderstanding external CI/CD integrationsRun external CI/CD jobsExternal CI/CD action reference
Introduction
Understanding release orchestrationManage applicationsCreate deployer workflowsCreate staged workflowsCreate and manage releasesOrchestrate multi-workflow releasesRelease management reference
Understanding artifact managementRegister and track artifactsStore and retrieve artifactsPromote artifactsGenerate a software bill of materialsArtifact management reference
Deploy with HelmDeploy to KubernetesContainer deployment reference
Deploy to AWSAWS deployment reference
Deploy with enterprise platformsExecute remote deployment commandsEnterprise deployment reference
Verify deployments with New RelicDeployment verification reference
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceEnable secret modeConfiguration as Code reference
Understanding flag impressions and activity statusUnderstanding flag healthUnderstanding code referencesReview and clean up feature flagsSet up code references
Understanding Jira integration for feature flagsSet up the Jira integrationLink Jira tickets to feature flags
Understanding multiple SDK keysBuild your first mobile app with feature flagsBuild your first feature-flagged web applicationBuild your first feature-flagged backend serviceInstall client-side SDKsInstall server-side SDKsConfigure multiple SDK keysFlag implementation reference
Backend SDK referenceGo SDK referenceJava SDK referencePython SDK referenceRuby SDK referencePHP SDK reference.NET/C# (server-side) SDK referenceNode.js SDK referenceMobile SDK referenceAndroid SDK referenceiOS/tvOS SDK referenceObjective-C SDK referenceSwift SDK referenceReact Native SDK referenceWeb SDK referenceJavaScript (browser) SDK referenceJavaScript SSR SDK referenceClient SDK referenceJava client SDK reference.NET/C# (client-side) SDK referenceC (server-side) SDK referenceC++ (server-side) SDK referenceC (client-side) SDK referenceC++ client SDK reference

View pending approval tasks in your inbox

2 minute read
How-to guide— Task-oriented: directions to achieve a specific goal.

The CloudBees Unify inbox displays workflow approval tasks waiting for your action. Access the inbox from the global header to see all pending manual job approvals and environment gate approvals scoped to your user account. The inbox shows only tasks that you are authorized to approve, based on the approvers configured for each job.

The inbox is read-only. You cannot approve or reject tasks directly from the inbox. To act on a task, select View workflow run to open the workflow run details page where you complete the approval.
The inbox, the AI Assistant, and the CloudBees Unify MCP Server all retrieve pending approval tasks from the same source. If you prefer, ask the AI Assistant to list them, or use an MCP-connected tool such as Claude to query them instead. Refer to AI Assistant prompts reference for example prompts, or CloudBees Unify MCP Server tool reference for MCP tool details.

Access your inbox

The inbox icon appears in the global header and displays a badge showing the count of pending approval tasks.

To open the inbox:

  1. Select the Inbox icon in the global header.

    The inbox panel opens and displays your pending approval tasks.

Identify tasks in your inbox

Before navigating to a workflow run, review each inbox item to confirm you are acting on the correct task.

  • Each item shows the workflow name and stage so you can identify where in the pipeline the approval is waiting.

  • Read the approval instructions to understand what the workflow author needs you to verify before approving or rejecting.

  • Check the relative timestamp to see how long the task has been waiting.

  • Use the context chips (organization, application, component, release, environment, and stage) to confirm the system and environment the approval affects.

To approve or reject a pending task, locate it in the inbox and then navigate to the workflow Run details page.

  1. In the inbox, locate the task you want to act on.

  2. Select View workflow run.

    The workflow run details page opens.

  3. Review the approval request and complete the approval from the run details page.

For information about the run details page, refer to Monitor workflow runs.

Check when no tasks appear

If the inbox displays an empty state message, you have no pending approval tasks. Close the inbox and continue your work. If you expected a task to be waiting, confirm with the workflow author that the approval job has been reached in the run.

Monitor workflow runs