How to Navigate the Cubyts Platform and Understand Its Workspace?

Introduction

This guide explains how to get started with the Cubyts platform and understand its workspace structure and core capabilities. By the end of this walkthrough, you will know how to log in, navigate a workspace, and use health, reports, flags, repositories, and integrations to gain real-time visibility and governance across your SDLC.

Prerequisites

• Access to the Cubyts platform

• Valid login credentials (email/password or enterprise identity)

• Membership in at least one Cubyts workspace

Step-by-Step Guide

Step 1: Log in to the Cubyts Platform

1. Open the Cubyts login screen using either:

   • The shared Cubyts identity URL, or

   • Your organization’s single-tenant hosted URL.

2. Sign in using:

   • Your email ID and password, or

   • An enterprise identity provider such as Google or Microsoft.

After successful authentication, you are taken directly into your Cubyts workspace.

Step 2: Understand the Workspace Concept

• A workspace represents a group of people working toward a common objective.

• This objective could be:

  • A customer project

  • A feature

  • A set of related features

• Each workspace acts as a single view for execution health, governance, and reporting.

Step 3: Review Execution Health

• The Health capability depicts and predicts the health of execution artifacts such as:

  • Portfolios

  • Epics

  • Sprints

  • Code repositories

• Health indicators give you real-time visibility into how work is progressing and where attention may be required.

Step 4: Explore Detailed Reports

• Reports allow you to deep dive into individual artifacts, including:

  • Team members

  • Work items

  • Teams

  • Pull requests

  • Branches

  • Repositories

• Reports are tightly linked to health indicators, enabling deeper analysis wherever risks or deviations appear.

Step 5: Use Governance Flags

• Flags act as governance indicators across the SDLC.

• They highlight different categories of drift, helping teams:

  • Detect risks early

  • Identify deviations from expected execution

  • Take corrective action before issues escalate

Step 6: Access the Repository

• The Repository capability automatically compiles and collects documents from connected tools.

• These documents are enriched with context and preserved for future reference, supporting audits, reviews, and knowledge continuity.

Step 7: Connect Your SDLC Tools Using Integrations

• The Integration Workflow connects Cubyts with your existing SDLC toolchain, including:

  • Planning tools such as Jira and Azure DevOps

  • Requirement and design tools such as Figma

  • Code repositories like GitHub, GitLab, and Bitbucket

• These integrations enable continuous analysis of SDLC artifacts to automatically discover execution and governance drifts.

How It All Comes Together

By combining workspaces, health indicators, reports, flags, repositories, and integrations, Cubyts provides:

• End-to-end visibility across the SDLC

• Early risk detection

• Continuous governance without manual overhead

Conclusion

You now understand how to log in to the Cubyts platform, navigate a workspace, and use its core capabilities to monitor execution health, analyze risks, and maintain governance across your SDLC. As a next step, explore health reports and flags in your workspace to see how Cubyts highlights actionable insights for your teams.

Video link: https://www.loom.com/share/d408e63098654247adc316edb54f0d7b