Organizations & Teams
EOS Hub uses a two-level hierarchy: Organizations contain Teams. This mirrors how EOS is typically implemented, with a company running EOS across its leadership team and departmental teams. One installation can host several organizations.
Organizations
An organization represents your company. It is the top-level container for all data in EOS Hub.
Each organization has:
- A name, a time zone (default Europe/Bratislava), and a default language for new accounts
- Members, each with an organization role: Owner, Admin, Member, or Implementer
- One or more teams
- Organization-wide data such as the company vision on the V/TO (with the core values) and company-level Rocks
Organizations are created by the platform operator in Platform administration, together with their first Owner. From then on, the organization's Owners and Admins manage its settings, people, and teams in Organization settings. On a new, empty installation, the onboarding wizard creates the first organization, and the first user becomes its Owner.
Organization Membership
People belong to an organization through an organization membership with a role:
| Org role | Access to teams |
|---|---|
| Owner, Admin | All teams of the organization, at least as team Admin (Owner where they are a team Owner); manage the organization |
| Implementer | All teams of the organization as team Admin, but never rates meetings |
| Member | Only the teams they belong to, with their team role |
A person can belong to several organizations and switch between them with the organization switcher in the sidebar header. See User Management for details.
INFO
Data never crosses organizations. The platform operator (SUPERADMIN) does not see an organization's teams unless they are also a member of it.
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 -- Admins and Owners of the leadership team edit the company vision, which every team's V/TO shows; the leadership team's V/TO lists the company Rocks of the quarter.
- Visibility -- The leadership team flag helps distinguish the primary EOS team from departmental teams.
TIP
Mark your leadership team in Organization settings > Teams with the Leadership team toggle on the team card.
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 by organization Owners and Admins:
- Navigate to Organization settings > Teams.
- Find the team's card.
- Choose an organization member in Add to team.
- Set their team role.
Only members of the organization can be added to its teams.
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 | Vision per organization (shared by all teams); Traction -- 1-Year Plan, Rocks, long-term issues -- per team |
| Accountability Chart | One for the organization (default for new organizations) or one per team -- chosen in Organization settings → General |
| 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 switch between them in the team menu of the top bar or with the team switcher in the sidebar. The team menu keeps the page you are on: from the Rocks of one team you go to the Rocks of the other. Dashboard, Scorecard, Rocks, and all other tools then show that team's data. Both list only the teams of the current organization; use the organization switcher to change organizations. See Navigating.
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
- Organization Settings & Platform -- Managing teams and members
- User Management -- Creating and managing users