Introduction
Understanding organizationsUnderstanding componentsManage organizationsManage componentsManage component Jira integrations
Set up your first organizationUnderstanding 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 notifications
Accessibility policy referenceShared responsibility model referenceSubscription and services agreementSupport policiesSupported browsers and external tools
Introduction
Understanding feature managementUnderstanding Configuration as CodeGet started with feature managementCreate and manage feature flagsConfigure feature flag targetingOrganize feature flagsImplement feature flag governanceConfiguration 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 keysMobile SDK referenceWeb SDK referenceBackend SDK referenceClient SDK referenceFlag implementation reference
Introduction
Understanding CI workflowsCreate a build workflowCreate and manage workflowsCreate reusable workflowsTest and validate containers in workflowsCheck out source codeTrigger workflows remotelyWorkflow syntax referenceJobs syntax referenceSteps syntax referenceServices syntax reference
Monitor 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 external secret providers
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

Set up your first CloudBees Unify organization

4 minute read

In this tutorial we will build a complete, working CloudBees Unify organization with verified access, team members, and connected source code integration. Along the way we will encounter organizational structure, team management concepts, and SCM integration workflows that form the foundation of software delivery automation.

By the end, you will have a functional organization and familiarity with the core elements that power CloudBees Unify workflows.

Before we begin

Before we begin, ensure you have:

  • An email address for account creation and verification.

  • Admin access to a GitHub repository for integration testing.

This tutorial uses GitHub as a working example because it requires no additional setup beyond OAuth authentication. All supported SCM providers (GitHub, GitHub Enterprise, Bitbucket, and Bitbucket Server) integrate with CloudBees Unify using the same pattern.

Create and verify your account

If you don’t already have a CloudBees Unify account, we start by creating one and verifying it works correctly. CloudBees Unify will automatically create your first organization during this process, giving us the foundation to build on throughout the tutorial.

  1. Navigate to https://cloudbees.io.

  2. If you don’t already have an account, select Sign up.

  3. Enter your email address and create a password.

    The system will create both your user account and your first organization automatically.

  4. Check your email inbox for a message with the subject "CloudBees Email Verification".

  5. Select Verify in the email, or copy and paste the provided link into your browser.

  6. Sign in to https://cloudbees.io with your credentials.

You will see the CloudBees Unify dashboard with your new organization context displayed in the top navigation. Notice that your organization name appears in the breadcrumb trail. This shows you are now working within your organizational boundary.

The dashboard is currently sparse because we haven’t added team members or integrations yet. We are about to change that.

Add your first team member

Now that our organization exists, we can invite others to collaborate. CloudBees Unify uses role-based access control (RBAC) to manage what each team member can do within the organization.

  1. From the left navigation, select Configurations.

  2. Select Users.

    You will see yourself listed as the organization admin with full access rights.

  3. Select Invite Users.

  4. In the email field, enter a test email address you have access to (this can be another email account you own).

  5. From the Team dropdown, select Users.

    Users is a system-generated starter team that CloudBees Unify creates automatically and provides read-only access to the organization. Refer to Understanding users and teams to learn about teams and how to create custom teams with different permissions.

  6. Select Send Invitations.

The invitation will appear in the team list immediately, showing "Pending" status. Notice that the user count in the interface updates to show your growing team size.

The invited user will receive an email with instructions to join your organization. We don’t need to wait for them to accept.

Connect your source code

Next we establish the development workflow foundation by connecting CloudBees Unify to your source code repository. This integration enables CloudBees Unify to monitor code changes and trigger automated workflows.

  1. From the left navigation, select Configurations.

  2. Select Integrations.

    You will see an empty integrations list. We are about to add our first one.

  3. Select Create integration.

  4. Select GitHub from the available SCM options.

  5. Enter github-integration as the integration name.

    We are using this exact name because we will reference it when discussing integration management.

  6. Select Create.

CloudBees Unify will redirect you to GitHub for authentication. GitHub will open in a new browser tab or window. This is normal and secure OAuth behavior.

  1. In the GitHub authentication window, select Authorize CloudBees to grant repository access.

  2. Select the GitHub organization that contains your test repository.

  3. Select Install & Authorize.

GitHub will redirect you back to CloudBees Unify where the integration setup completes automatically. You will see the integration status change to "Connected" with a green indicator.

The integration now appears in your Components section with automatic webhook configuration completed. Notice that CloudBees Unify can see your repository structure and is ready to respond to code changes.

Verify your working organization

Let’s confirm that all three foundation elements are functioning correctly before we conclude. A complete organization should show verified access, team management, and source code connectivity.

  1. Navigate to the organization home page by selecting the CloudBees Unify logo in the top navigation.

  2. Review the organization dashboard.

You will see indicators showing: * Your verified account status and organization membership. * Team member count including your pending invitation. * Connected integrations with your GitHub repository visible.

Notice that the dashboard now displays available actions like "Create workflows" and "Invite more users". These options appear because CloudBees Unify detects you have the necessary foundation elements in place.

The organization overview confirms that your setup is complete and ready for software delivery automation. Everything is now connected and communicating properly.

Next steps

We have created a functional CloudBees Unify organization with verified account access, team member invitations, and GitHub integration. Along the way we encountered organizational navigation, RBAC concepts through team assignment, and SCM integration workflows.

You now have a working foundation and the vocabulary to expand your CloudBees Unify setup confidently.

From here, you might want to:

Related pages

Understanding CloudBees Unify features
Connect your CI tool