Oracle Visual Builder Studio Project Dashboard – How to Navigate and Manage Projects

This guide introduces the Projects Dashboard in Oracle Visual Builder Studio, a cloud-based development platform used for building, testing, and deploying modern applications. The screenshot shows a real workspace where multiple projects—such as training apps, test workspaces, and visual applications—are organized in a unified view.

From this central dashboard, developers can quickly access project details, monitor status, track updates, and manage members. Each project displays key information like activity status, last updated time, and disk usage, helping teams maintain clarity and control over their development environment.

Whether you’re a beginner exploring Oracle Visual Builder Studio for the first time or a team member managing multiple workspaces, this page acts as the command center for organizing all project-related activities.

Active Workspace or Projects

Existing development projects like the ones shown:

1. Aditya_S_Test
2. MK_CX_WORKSPACE
3. test_poc
4. VBCS_TRAINING
5. VisualApp-ora001

Internet Browser

Chrome, Edge, or Firefox for best Visual Builder Studio performance.

Stable Internet Connection

Required for loading repositories, builds, and project updates.

Basic Developer Access

Permissions to view projects, check status, and create or modify work items.

The Oracle Visual Builder Studio (VBS) Project Dashboard, which serves as the central workspace for managing development projects inside an organization. This interface provides a clear overview of all active projects, their statuses, templates, members involved, and the disk space each project consumes.

At the top, you can see the organization name, indicating the environment or workspace where all these projects are hosted. Visual Builder Studio organizes everything under a centralized structure, making it easy for developers, designers, and administrators to collaborate efficiently.

The screen displays a total of five active projects, each listed with important metadata such as:

1. Project Name – The unique identifier of the application or workspace
2. Template Used – Helps identify the type of project setup
3. Favorite Option – Allows marking frequently used projects
4. Status – Shows whether the project is Active or Idle
5. Last Updated Date – Indicates recent activity
6. Members – Displays who is currently part of the project
7. Disk Usage – Helps monitor resource consumption

On the top right, you also have the option to create a new project, an essential feature when starting fresh development activities. This enables developers to spin up a new workspace instantly.

The left navigation bar includes multiple sections like:

1. Workspaces
2. Git
3. Merge Requests
4. Docker
5. Builds
6. Environments
7. Issues
8. Boards
9. Snippets

These features make Visual Builder Studio a complete DevOps platform, allowing teams to handle version control, CI/CD pipelines, deployment automation, issue tracking, and more—all in one place.

Overall, this dashboard provides a clean and organized summary of your development landscape, helping you quickly understand project health, usage, and activity at a glance.

1. Workspaces

This area is where developers build and design applications.

It highlights:

1. Your active workspace
2. A button to view or switch workspaces
3. Information about how workspaces function in app development

Workspaces act as your private development environment where you can design web apps, mobile apps, and service extensions.

2. Environments

The Environment panel displays:

1. The deployment stage (for example, Dev)
2. The current environment status
3. Any updating or deployment processes

This section helps beginners track where the app is hosted and what version is currently running.

3. Recent Activities

This area shows the latest commits, builds, pipelines, and deployment actions.

You can see:

1. Build results
2. Code commits via Git
3. Pipeline execution status
4. Developer activity timestamps

This helps teams stay updated on ongoing work across the project.

4. Team Section

On the right side, you can view project members along with their roles:

1. Project Owner
2. Developer
3. Developer Limited
4. Contributor

This helps in understanding who has access and who is responsible for which part of the project.

In this step, we explore the environment section of the project, which displays all the active service instances connected to the Visual Builder Studio setup. The page shows a dedicated environment named Dev, and within this environment, two service instances are listed. Each instance provides essential operational information that helps developers ensure the system is healthy and ready for deployment.

The first instance represents the Visual Builder Runtime Endpoint. This component is used to run applications created within the development workspace. Alongside the instance name, the interface displays the operational status and the latest response time, allowing the user to quickly verify that the runtime environment is performing within acceptable limits.

The second instance is associated with Oracle Applications Cloud (Fusion). This indicates a direct link between the Visual Builder project and Fusion applications, supporting integration-based development. Just like the runtime endpoint, this instance also shows its availability and response time, enabling developers to monitor its readiness for extension development or API interactions.

Both instances include a Details option, which allows deeper inspection of configuration, metrics, and connectivity. This structure helps developers maintain control over the environment, identify issues before deployment, and confirm that all dependent services are functioning properly. Having these instances clearly displayed improves the workflow and ensures that development activities proceed without interruption.

The Releases section represents the versioning and distribution layer of your Visual Builder Studio project. This area is designed to help teams package, track, and distribute stable versions of their applications or components. When you access the Releases panel for the first time in a new project, it typically appears empty, indicating that no official release has been created yet.

A release in Visual Builder Studio is more than just a tag or a bundle of files. It acts as a controlled milestone that captures the most stable snapshot of your application at a specific point in time. Creating a release ensures that every team member, stakeholder, or automated process can reliably download the same version of the codebase without worrying about changes happening in the background.

The interface provides a clean layout with a clear call to action to create your first release. Before a release is created, developers often complete tasks such as source code validation, build pipeline execution, and issue tracking to ensure the project is in a ready state. Once a release is generated, it becomes accessible in this section, where you can review its metadata, download artifacts, or promote it to different environments.

This step is particularly important for projects that require structured delivery cycles. It helps maintain consistency across builds, reduces deployment risks, and supports collaborative workflows where multiple developers are working on different features. Even though this page currently shows no available releases, it is a foundation for maintaining application stability and preparing your project for deployment across various environments.

This step focuses on the Projects Overview section inside Visual Builder Studio. The interface provides a clear, structured view of all the active projects within the organization, helping teams quickly understand the status and activity of each workspace. The layout is designed to offer both high-level information and detailed operational insights in one place.

At the top, filters such as Member, Favorites, Owner, and Shared allow you to refine project visibility based on your role or involvement. This makes navigation much easier, especially for developers managing multiple projects simultaneously. The search bar adds another layer of convenience, enabling users to locate projects by name without manually scanning the list.

The main table presents several important attributes for each project. The Name column lists all available projects, each representing a different development effort or workspace. The Status column provides real-time information showing whether a project is currently active. The Updated column helps track recent changes, making it easy to identify which projects are being worked on and which may require attention.

Another useful element is the Members column, which displays the team members assigned to each project. This is especially valuable when working in collaborative environments, as it quickly reveals responsibilities and contact points. The Disk Usage column highlights storage consumption, allowing administrators and developers to monitor resource usage and prevent any potential capacity issues.

The create button in the top-right corner allows users to initialize new projects quickly. This streamlined approach supports agile development practices, reducing the delays typically associated with setting up new work areas.

Overall, this page serves as the operational hub for managing multiple development streams. It offers a well-structured combination of project management, visibility, and resource tracking, all essential for maintaining efficient workflows in Visual Builder Studio.

In this step, the Visual Builder Studio interface presents the project creation form, where you begin defining the core identity of your new project. This screen appears immediately after selecting the option to create a new project, and it represents the foundation for how your project will be managed, shared, and organized inside the workspace.

The form highlights two key fields: the project name and the project description. The project name is mandatory, as it becomes the primary identifier for your work. A clear and meaningful name helps team members quickly recognize the purpose of the project. Below the name field, the description area allows you to provide additional context—this may include the project’s goals, the type of application being built, or any requirements the team should be aware of. Although optional, a well-written description improves communication across the team and sets expectations from the start.

The lower section of the form focuses on project visibility and access controls. You can choose to keep the project private or make it shared across the organization. Private projects limit access to assigned members, while shared projects are visible to everyone within the environment. An additional option labeled Discoverable allows others in the organization to search for the project, making collaboration easier when working across teams.

Once the initial details are completed, you can move forward by selecting the Next option. This continues the setup process, leading into template selection, configuration settings, and team assignment in the following steps. This stage is critical because it establishes the project’s structure and ensures your development work begins with clarity and proper organization.

The Project Home page provides a consolidated view of everything connected to the selected Visual Builder Studio project. This page acts as the central dashboard where developers, team members, and project owners can quickly understand the project’s current state, resources, and activity flow.

The upper section highlights the Workspaces area. A workspace is a dedicated environment where application development takes place. It allows team members to build mobile apps, web apps, and extensions with isolation and control. From this section, users can access their workspace directly or explore guidance on how workspaces function inside Visual Builder Studio.

Below the Workspaces section is the Environments panel. An environment represents a connection to Oracle Cloud services that the project interacts with. Through this interface, users can create environments that link to platform services, test instances, or cloud applications. This ensures the project is able to deploy, test, and integrate with cloud services in an organized and secure way.

On the right side, the Team section lists all members associated with the project. Each user is assigned a specific role such as Project Owner, Developer, or Contributor. This area helps maintain visibility into who has access and what level of responsibility they hold within the project. Team roles play a key role in code management, build permissions, and deployment workflows.

Towards the bottom, the Recent Activities panel provides a chronological summary of what has been happening in the project. This includes actions such as code pushes, environment updates, builds, or administrative changes. It helps teams stay informed about progress and quickly identify updates made by other collaborators.

Overall, the Project Home page offers a structured view of the project’s operational components, ensuring smoother collaboration, easier navigation, and improved understanding of the project's development lifecycle.

In this step, you are taken to the Workspaces section of Visual Builder Studio. The interface indicates that no workspace has been created yet for this project. A workspace is an essential component in Visual Builder because it connects your project to the version control system, environments, and design tools you will use while building applications.

Here, you are presented with options to begin setting up your workspace. The system offers three primary choices: create something new, import an existing setup, or clone a repository from Git. Selecting the New option opens two creation paths. The first path allows you to create a New Visual Application, which is ideal if you are starting a fresh web or mobile application. The second option is to create a New Application Extension, commonly used when you want to enhance or extend existing Fusion Applications.

This screen is the beginning point where you define how your application development flow will proceed. By choosing the appropriate option, you set up the structure, tools, and foundation required for the rest of your project. Once a workspace is created, you gain access to the Designer, Git integration, environments, and all development features needed to build and deploy your applications.

In this step, the screen displays the main application dashboard inside Oracle Fusion. This dashboard acts as the central entry point for users to access a wide range of business functions, depending on the roles and permissions assigned within the organization. The layout is organized into distinct sections, allowing users to quickly identify and launch the tools they need.

At the top of the interface, the navigation bar groups key modules such as Sales, Redwood Sales, Service, My Team, Procurement, My Client Groups, Help Desk, and Product Management. These categories help users move between different business areas efficiently without needing to search manually. Each section expands into specialized features tailored to its functional domain.

In the central part of the page, the dashboard highlights a grid of application tiles. These tiles represent the operational capabilities available to the user, including Workspaces, Activities, Deal Registrations, Leads, Opportunities, Forecasts, Accounts, Contacts, Lightbox, and Analytics. Each tile is clearly labeled, making it easy to understand what type of information or action resides within that module. This tile-based layout improves user productivity by reducing the number of clicks required to reach a specific function.

On the left side, a dedicated Quick Actions panel allows users to perform frequently needed tasks, such as creating contacts, appointments, tasks, call reports, opportunities, or leads. These quick-start options are particularly helpful for users who perform high-volume or repetitive actions throughout the day. By providing shortcuts to essential functions, the system streamlines workflow and minimizes navigation time.

The design of this dashboard is intentionally simple and structured. It focuses on delivering clarity and ease of use, especially for users who manage various customer and sales-related activities. With clean tiles, grouped modules, and quick-action tools, the dashboard guides users through their daily operations in a predictable and organized manner.

At this stage of the setup, the platform presents a list of available application templates that serve as the foundation for your new Visual Builder project. This step is important because the template you choose will define the initial structure, layout, components, and preconfigured features of your application. Each template is designed to support different use cases, so selecting the right one ensures your project begins with the correct architecture.

The interface displays a collection of templates arranged in a clear, scrollable panel. The first option is the Default VB Application, which provides the most basic and flexible starting point, ideal for users who want full control over their project design. Alongside this, several Digital Customer Service templates appear, each tailored for specific Engagement Cloud releases. These templates come with predefined pages, data flows, and user interface elements that support customer service scenarios.

There is also a Redwood Starter template available. This template includes preconfigured Redwood design elements and is particularly useful for teams that want to adopt Oracle’s modern design system across their application. Each template card includes a version number and a brief description to help you evaluate suitability before making a selection.

After reviewing the options, you can choose the template that best aligns with your requirements. The process continues by clicking the selection button, which will configure the project workspace with the defined structure, allowing you to proceed into the development phase with a consistent framework already in place.

After creating and opening your visual application, you are taken to the Welcome Dashboard. This landing page serves as the central starting point for building, configuring, and enhancing every part of your application. It provides a structured layout that helps new developers quickly understand where to begin and how different components fit together.

At the top of the page, you are greeted with an overview message that confirms the name of your application and outlines its purpose. The welcome text highlights that the application may contain multiple responsive apps, service connections, business objects, and additional artifacts required to support functionality.

On the main panel, the dashboard is divided into three primary sections: Create Apps, Connect to Data, and Add Artifacts. Each section guides you through the essential building blocks of a visual application. The Create Apps section allows you to start building responsive applications that work across desktops and mobile devices. This is where you define the pages, layouts, and user interface interactions that form the visual experience of your solution.

The Connect to Data section provides access to tools for setting up service connections. This is where you connect to REST endpoints or other backend services, enabling your application to retrieve, update, and manage real-time data. Along with service connections, you also have the option to create business objects, which are useful for defining structured data models within your app itself. These objects can generate REST endpoints automatically, giving you a flexible way to store and retrieve information.

The Add Artifacts section offers the ability to include additional components that extend your application. These components may involve reusable UI pieces, logic modules, or supporting resources that help streamline development and maintain consistency across pages.

On the right side of the dashboard, a dedicated learning panel provides quick access to documentation, tutorials, and navigation guides. This section is especially helpful for beginners who want to understand how different tools in the Designer work. It also includes links for managing applications, controlling source code, and referencing sample apps available through GitHub.

The Welcome Dashboard acts as both an instructional guide and a development hub. It brings together all the foundational tools and resources needed to begin building your application, ensuring that even new developers can transition smoothly into the development workflow.

In this step, you configure and attach an Oracle Cloud Applications service instance to your Visual Builder project. The interface displays the available instance types on the left and the discovered instances on the right, allowing you to select the correct application resource for your environment.

Begin by choosing the instance type. Since this project is intended to connect with Oracle Fusion Applications, select the Oracle Cloud Applications option. This ensures the platform presents only the relevant Fusion environment resources that your project can use for service connections, data models, and integration points.

Next, select the method for adding the instance. Using the Instance List option makes the process more streamlined, as it automatically pulls all available application instances associated with your identity domain. This avoids the need to manually enter credentials and reduces the possibility of configuration errors.

On the right side, the system displays the available instance under the Instance List. Here, the Oracle Applications Cloud (Fusion) resource appears as a selectable item. This resource will allow your Visual Builder application to authenticate, access Fusion modules, and interact with business objects securely. Review the instance type, confirm that the domain and resource type are correct, and select the checkbox to include it.

Once the instance is selected, you can proceed to add it to the project. This step completes the connection setup, enabling your application to consume REST services and work with Fusion data in subsequent development steps. After this configuration, you will be ready to define service connections, build integrations, and use Fusion objects within your visual application.

In this stage, the interface displays the section for adding a new service instance, specifically focused on locating available Visual Builder runtimes within the tenancy. The page clearly separates the configuration options on the left from the instance results displayed on the right, allowing you to verify whether a suitable runtime environment is available for integration.

On the left panel, you can see that the instance type is set to Visual Builder, which means the system will attempt to locate any existing Visual Builder runtimes associated with your chosen region and identity domain. The option for adding the instance using the instance list is already selected, enabling Visual Builder Studio to automatically fetch the available runtimes without requiring manual credential entry.

Below this section, the OCI details show the tenancy region and root compartment, confirming that the search is being performed in the correct environment. This information is important because Visual Builder runtimes are region-specific, and selecting the correct compartment helps ensure accurate results during the discovery process.

The right panel displays the results of the instance search. In this case, the system indicates that no Visual Builder runtimes are available in the selected region and identity domain. This can occur if Visual Builder has not been provisioned yet or if it exists under a different identity domain or compartment. Without an available runtime, integration with Visual Builder services cannot proceed, and a new instance may need to be provisioned before continuing.

This step helps verify infrastructure availability early in the setup process, ensuring that the project is correctly connected to the required backend services before moving deeper into application development or integration workflows.

At this stage, the platform displays a dialog informing you about the current Git integration status of your visual application. The message clearly states that the application has not yet been linked to a Visual Builder Studio repository or branch. This step is important because Git integration enables version control, collaborative development, and maintains a historical record of all changes made to the project.

The dialog provides an option to proceed with linking your application. Selecting the link option allows you to associate the project with an existing repository or configure a new one within Visual Builder Studio. This ensures that all future updates, feature changes, and configurations are captured in a structured and trackable manner. If you are not ready to configure Git immediately, you can dismiss the dialog for now and return to this setup later from the development workspace.

This step reinforces the importance of source control in application development, especially in collaborative environments where multiple contributors may be working on the same project. Enabling Git integration early in the process helps prevent configuration drift and provides a consistent workflow for committing, reviewing, and managing changes.

After completing the workspace creation and linking process, the Project Home page provides a consolidated view of everything configured within this Visual Builder Studio project. This screen is essential because it shows the current state of your workspaces, environments, team roles, and ongoing activities in one structured dashboard.

At the top, the Workspaces section confirms that your active workspace has been created successfully. The workspace name appears along with the associated Git repository and the environment mapped to it. You can also see when the workspace was last opened, which is useful when multiple developers collaborate and want to track recent activity or resume work exactly where they left off. The Manage Workspaces option allows you to perform additional configuration or handle multiple workspaces within the same project.

Below that, the Environments panel lists the development environment linked to your project. Since this stage usually occurs early in setup, you may see zero service instances connected yet. This is expected and indicates that upcoming steps will involve adding service instances such as Oracle Cloud Applications, Visual Builder runtimes, or Integration Cloud connections depending on your project requirements.

On the right side of the page, the Team section displays the members currently associated with the project. Every member is categorized based on their assigned role, such as Project Owner, Developer, Developer Limited, or Contributor. This clear classification helps maintain structured access control and ensures that each user has the appropriate level of permissions. The Add Member option is available for administrators to include additional collaborators whenever needed.

At the bottom, the Recent Activities panel provides a chronological log of all project operations. This includes environment creation, workspace creation, version control operations like Git commits and pushes, and any automated processes triggered within the system. This activity feed is especially valuable for teams because it gives visibility into who performed each action and helps in tracking progress or identifying issues during development.

Overall, this step provides a complete overview of the project’s operational status. It confirms that your workspace is live, your environment is active, and your project structure is ready for development to continue smoothly.