What is the Workspace
The Leavory Workspace (app.leavory.com) is the engineering governance portal, Leavory’s subscription product. It connects to your Azure DevOps organization, discovers everything automatically and brings together what is scattered today across many tools and spreadsheets.
| Question | What the Workspace shows |
|---|---|
| What exists and who owns it? | Inventory of projects, repositories, branches, pipelines, packages and technologies |
| How are teams delivering? | Pipelines and runs, failures, stalled pipelines and delivery metrics per project |
| Which project needs attention? | Health of each repository and project, combining delivery, reliability and security |
| Who can change what? | Groups and members of each Azure DevOps project |
| What is actually dangerous? | Trivy, Sonar and OWASP Top 10 in one dashboard, with active exploitation and the age of each flaw |
| What is running in production? | Images from registries and Kubernetes clusters, with each one’s vulnerabilities |
| How do I fix it? | Ask Leavory, the AI assistant that explains each finding and what to change first |
The value is in the cross-cutting view: the repository with the most critical flaws may be the same one whose pipeline has been stalled for weeks and whose project has too many admins. Each tool on its own shows only one piece of that.
Access
Section titled “Access”- Access is per organization (tenant). The tenant owner adds new users, up to the plan’s user limit.
- The Workspace asks for the authenticator code on every entry, even if you’re already signed in to the Hub.
- Without granted access, the screen shows You don’t have access yet. There are two ways in:
- Your company already has a plan: ask the tenant owner to add you. Then just sign in again.
- Your company doesn’t have a plan yet: fill in Company (and, optionally, a Message with your team, how many people and what you want to see first) and click Request access. The request is reviewed, the answer comes by email and, once access is granted, just sign in again.
First step: connect Azure DevOps
Section titled “First step: connect Azure DevOps”The Workspace reads your organization with a read-only PAT, with five scopes. See which ones and how to set it up in Connect Azure DevOps.
| Item | What it’s for |
|---|---|
| Dashboard | Overview of the organization |
| Vulnerabilities | Every vulnerability found, prioritized |
| Notifications | Alerts and recent activity |
| Code & Pipelines → Projects | The organization’s projects |
| Code & Pipelines → Repositories | Repositories, with packages and Exposure Age tabs |
| Code & Pipelines → Packages | Packages and dependencies used in the repositories |
| Code & Pipelines → Pipelines | Pipelines and their runs |
| Code & Pipelines → Dockerfile | Base images used in Dockerfiles and their findings |
| Code & Pipelines → Exposure | Repository exposure |
| Kubernetes | Clusters and each one’s findings |
| Container Registry | Registry images and their vulnerabilities |
| AppSec → Config Stack | Configuration generators, including the Security Gate step |
| AppSec → Sonar Analysis | Static analysis results |
| AppSec → Vulnerability Lookup | Look up a CVE and see what it affects in your organization |
| Settings | Tenant settings, including the Azure DevOps connection |
| Administration | Tenant users, for the owner |