1. 1 Introduction
2. 1.1 Terms of Service
3. 1.2 Privacy
4. 1.3 Support
5. 2 Logging in and getting started
6. 2.1 Understanding the difference between the basic and webhook enabled apps
7. 3 Workspaces
8. 3.1 Members administration and access levels
9. 3.2 Hierarchy naming schemes
10. 3.3 Free versus paid licences
11. 3.4 Organizations within a workspace
12. 4 Organizations
13. 4.1 Repos
14. 4.1.1 Mapping an organization to a collection of repos
15. 4.1.2 Setting up ignoring and scanning repos
16. 4.1.3 Supported languages and component discovery
17. 4.1.4 Specific repo page
18. 4.2 Components
19. 4.2.1 Specific component page
20. 5 Roadmap

Organizations

An organization in the Dashboard maps to a collection of repositories. It is the main operational unit for repository discovery and scanning.

What you manage at organization level

On the organization page you can typically:

• review repos,
• decide whether repos should be scanned or ignored,
• inspect repository scan status,
• and manage organisation-level defaults such as the scan state for newly discovered repositories.

Why organizations matter

This is where the Dashboard connects your source-control reality to the portal model. Once an organization is configured correctly, the rest of the dashboard becomes much more useful because repos, components, and dependencies all start from this point.