Scopes and Hierarchy
Understand how projects, teams, and organizations relate to each other in Evergreen.
Evergreen organizes your work into three nested scope levels. Understanding this hierarchy helps you put the right information in the right place and find it again easily.
The Three Scopes
Organization
└── Team(s)
└── Project(s)
Organization
The top-level container for all your work. An organization represents your company or account and contains all teams and projects. Organization-level roadmap initiatives and objectives are visible to all members.
Team
A group of people working across one or more related projects. Teams allow you to aggregate roadmap initiatives and objectives across their projects without creating org-wide visibility.
Project
A single website or digital property connected to Evergreen. Projects are the most granular scope — crawls, audits, and sitemaps are always project-specific.
Why Scope Matters
Several Evergreen features are scope-aware, meaning you can create and view them at whichever level is appropriate:
| Feature | Project | Team | Organization |
|---|---|---|---|
| Visual Sitemap | ✅ | — | — |
| Content Audit | ✅ | — | — |
| AI Insights | ✅ | — | — |
| Ask Eve | ✅ | — | — |
| Roadmap Initiatives | ✅ | ✅ | ✅ |
| Objectives & Key Results | ✅ | ✅ | ✅ |
Each initiative or objective must belong to exactly one scope. You cannot assign the same item to both a team and a project simultaneously.
Aggregated Views
When you open the Roadmap or Objectives at the team or organization level, Evergreen aggregates items from all projects within that scope:
- Team view — shows team-scoped items plus items from every project belonging to the team.
- Organization view — shows org-scoped items plus items from every project in the organization.
You can use the project filter and scope toggle to narrow these views. See Views and Filters.
Account Types and API Access
When using the MCP Server or OAuth 2.0 API, Evergreen uses two distinct account types that affect how projects are resolved.
Personal Accounts
When you sign up for Evergreen, you receive a personal account identified by a user_* ID. Projects created under a personal account are stored without an organization affiliation — they belong to you directly.
- Personal-account API keys and OAuth tokens carry your
user_*ID. - Evergreen resolves project access by looking for projects where no organization is set and the project was created by your user ID.
Organizations
Organizations are collaborative workspaces identified by an org_* ID. Projects created inside an organization are stored with the organization's ID.
- Organization API keys and OAuth tokens carry the
org_*ID. - Evergreen resolves project access by looking for projects where the organization ID matches the key's account ID.
Project Ownership Rules
| Account type | Project lookup strategy |
|---|---|
Personal (user_*) | organizationId is unset and createdByUserId matches your user ID |
Organization (org_*) | organizationId matches the organization ID |
A project created under your personal account is not visible to an organization key, and vice versa — even if you are a member of that organization.
