Organizations & Teams
EOS Hub uses a two-level hierarchy: Organizations contain Teams. This mirrors how EOS is typically implemented, with a single company running EOS across its leadership team and departmental teams.
Organizations
An organization represents your company. It is the top-level container for all data in EOS Hub.
Each organization has:
- A name and optional description
- One or more teams
- Organization-wide data such as the V/TO, company-level Rocks, and core values
INFO
In the current version of EOS Hub, each deployment typically serves a single organization. Multi-organization support is designed into the data model for future use.
Teams
Teams are the primary working unit in EOS Hub. Every EOS tool -- Scorecards, Rocks, Issues, Meetings, and To-Dos -- is scoped to a team.
Team Properties
| Property | Description |
|---|---|
| Name | Display name for the team |
| Description | Optional description of the team's purpose |
| Leadership Team | Flag indicating this is the senior leadership team |
Leadership Team
One team in each organization should be designated as the Leadership Team. This flag affects:
- Company-level Rocks -- Only the leadership team can own company-level Rocks.
- V/TO -- The V/TO is tied to the leadership team.
- Visibility -- The SUPERADMIN can see all teams, but the leadership team flag helps distinguish the primary EOS team from departmental teams.
TIP
Mark your leadership team in the admin panel under Teams > Edit Team > Leadership Team toggle.
Team Membership
Users are connected to teams through TeamMember records. Each membership has a role that determines what the user can do within that team.
A user can belong to multiple teams with different roles in each. For example, a user might be an OWNER of the leadership team and a MEMBER of the marketing team.
Adding Members
Team members are managed through the admin panel:
- Navigate to Admin > Teams.
- Select a team.
- Click Add Member.
- Choose a user and assign their role.
See Roles & Permissions for details on what each role can do.
Data Scoping
All EOS data in EOS Hub is scoped to a team:
| Data | Scope |
|---|---|
| Scorecard measurables | Per team |
| Rocks | Per team (company or department level) |
| Issues | Per team |
| To-Dos | Per team |
| L10 Meetings | Per team |
| V/TO | Per team (typically leadership team) |
| Accountability Chart | Per team |
| People Analyzer | Per team |
When a user switches between teams (if they belong to more than one), they see the data for the selected team only.
Team Switcher
Users who belong to multiple teams see a team switcher in the application sidebar. Selecting a different team updates the entire view -- Dashboard, Scorecard, Rocks, and all other tools -- to show that team's data.
Example Structure
A typical EOS Hub setup might look like this:
Acme Corp (Organization)
├── Leadership Team (Leadership flag: ON)
│ ├── CEO (OWNER)
│ ├── COO (ADMIN)
│ ├── VP Sales (MEMBER)
│ ├── VP Marketing (MEMBER)
│ └── VP Engineering (MEMBER)
├── Sales Team
│ ├── VP Sales (OWNER)
│ ├── Sales Manager (ADMIN)
│ └── Sales Reps (MEMBER)
├── Marketing Team
│ ├── VP Marketing (OWNER)
│ └── Marketing Coordinators (MEMBER)
└── Engineering Team
├── VP Engineering (OWNER)
├── Tech Lead (ADMIN)
└── Engineers (MEMBER)Next Steps
- Roles & Permissions -- Understand what each role can do
- Admin Panel -- Managing teams and members
- User Management -- Creating and managing users