Project and Collection hierarchies

Projects Overview

A Project is an all-encompassing entity to enable users to easily organize and navigate Collection hierarchies, and easily access insights associated with specific collections.

Projects provide an intuitive outlook for defining and managing your organizational hierarchies. By default, a Project consists of two top-level collection categories: namely Teams and Sprints, each with options to customize. Each collection category can have other collections defined under them in parent-child relationships.

Projects also empower admins to quickly associate all relevant product integrations under a project, and collections under this project are designed to automatically inherit these integrations.

For information about configuring Projects, go to Manage Projects.

Collection hierarchies & Inheritance

Collection hierarchies in SEI keep data organized. At the top of the hierarchy is a SEI project. Under each project are Collection categories and one or more levels of Collections.

  • SEI project: The umbrella for the SEI Collection hierarchy. Collection categories and Collections exist under their associated project; they don't span across projects. While multiple projects can have Collection categories and Collections with the same name, these are distinct groups under their designated project.

  • Collection categories: Broad classifications that serve as containers for Collections but are not, themselves, Collections. For example, Teams is a Collection category; whereas Engineering Team and Docs Teams are Collections under the Teams category.

  • Collections: Groupings, or narrow classifications, that are subdivisions of Collection categories. Each Collection category also has one root group which is the All Collection. For example, the root Collection for the Teams category is All Teams.

Projects, Collection categories, and Collections provide a broad way of organizing, filtering, and scoping data so you can examine data for different teams, lines of business, development initiatives, sprints, or other scopes. From there, you can configure metrics and reports to further refine and examine different facets of your teams' data.

Collection categories

Collection categories are broad classifications that serve as containers for Collections but are not, themselves, Collections. For example, Teams is a Collection category; whereas Engineering Team and Docs Team are Collections under the Teams category.

Each project has two default Collection categories: Teams and Sprints. You can modify the default categories and create custom categories.

The Projects Collection category is not the same as your SEI projects. This category is meant to represent sub-projects under the umbrella of the SEI Project. For example, if your SEI projects align with apps that you develop, then your sub-projects could be epics, components, or Jira projects.

For information about configuring Collection categories, go to Manage Collection categories.


Under each Collection category are one or more levels of Collections. Collections are groupings, or focused classifications, that are subdivisions of Collection categories. Inheritance flows down the Collection levels. For example, all Collection categories and Collections automatically inherit integrations from the associated project.

By default, each Collection category has one root, or All, Collection node. For example, the Teams category automatically has an All Teams Collection. Under the root node, you can create any number of Collections and Collection levels.

For example, in the Teams category, assume that you have a Collection for your Engineering teams, and you then create a child Collection for the Front End team under the Engineering teams Collection. The Front End team Collection inherits all Insights associated with the parent Collection (the Engineering team Collection). The resulting hierarchy might look like this:

  • Project

    • Teams (Collection category)

      • All Teams (Root Collection)

        • Engineering teams (Parent Collection)

          • Front End team (Child Collection)

          • Other Engineering teams...

        • Other teams...

For information about configuring Collections, go to Manage Collections.


Contributors are developers and other team members who complete actions and activities that contribute to your SEI metrics and insights. Contributors are represented by contributor records in SEI. SEI contributor records associate-related user accounts across your SDLC tools and can be used to populate contributor-based Collections.

For information about managing contributors, go to Manage Contributors.

Last updated