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 within a workspace

Organizations sit inside a workspace. Each organization is mapped to a collection of repos. Initially, that is the repos belonging to a GitHub user.

Relationship to workspaces

A workspace will in time support multiple organizations. That will allow one team or business area to keep related collections of repos together, while sharing workspace-level configuration.

Why group organizations together?

Keeping organizations in one workspace is useful when they share:

• the same administrators,
• the same hierarchy naming scheme catalogue,
• the same reporting context,
• or the same billing context.