User Management
EOS Hub manages people on two levels: organizations (your company) and teams inside an organization. Each person has a role in the organization and, in the teams they belong to, a team role. This page covers organization roles, adding people, team membership, and team permissions.
Organization Roles
Every member of an organization has exactly one organization role:
| Role | Description |
|---|---|
| Owner | Manages the organization (settings, people, teams). Acts as team Admin in every team of the organization -- or Owner where they are a team Owner. Can grant and revoke Owner and Admin. |
| Admin | Manages the organization (settings, people, teams). Acts as team Admin in every team of the organization -- or Owner where they are a team Owner. |
| Member | Sees and works only in the teams they belong to, with their team role (Owner, Admin, Member, or Viewer). |
| Implementer | An external EOS Implementer or coach. Acts as team Admin in every team of the organization, but does not rate meetings and cannot manage organization settings or people. |
WARNING
Only Owners can grant or revoke the Owner and Admin roles. An organization must always keep at least one Owner -- the last Owner cannot be demoted or removed.
The Implementer Role
The Implementer role is meant for an external EOS Implementer who coaches the company. An Implementer:
- Sees every team of the organization.
- Can facilitate L10 Meetings and manage Rocks, the Scorecard, issues, to-dos, the V/TO, and the Accountability Chart -- just like a team Admin.
- Does not rate meetings. The meeting rating belongs to the team, so Implementers are not listed in the ratings and do not count toward the "rated" total.
- Cannot change organization settings or manage people and teams.
Organization Switcher
People can belong to several organizations. The sidebar header shows an organization switcher with the current organization's name and your role in it. Open it to switch to another organization; your choice is remembered for your next visit.
If you open a link to a team of another organization you belong to, EOS Hub switches to that organization automatically.
INFO
A signed-in user who is not a member of any organization sees a No organization yet page. Ask an organization Owner or Admin to add you.
Adding People
Organization Owners and Admins add people in Organization settings > Members:
- Click Add member.
- Enter the person's email.
- If an account with that email already exists, it is added to the organization directly.
- Otherwise, a new account is created for that email (optionally enter the person's name). The person signs in with Google using that email address -- organization admins never set or know anyone's password.
- Choose the organization role and confirm.
| Field | New account | Existing account |
|---|---|---|
| Required | Required | |
| Name | Optional (filled from the Google profile on first sign-in) | Not needed |
| Role | Required | Required |
Password accounts
Email invitations, where people choose their own password, are planned for the next release. Until then, an account with a password can be created only by the platform operator (for an organization's first Owner).
New accounts start in the organization's default language.
TIP
After adding someone to the organization, add them to one or more teams in Organization settings > Teams. A Member without team membership sees no teams.
Google Sign-In
If Google OAuth is configured, people can also sign in with their Google account without being added first. A new account is created automatically, but it belongs to no organization -- the person sees the No organization yet page until an Owner or Admin adds them by email.
When an account was created as Google sign-in only, the first Google sign-in links the existing account to the Google profile and updates the name and profile picture. Organization and team memberships are preserved.
Changing Roles and Removing People
In Organization settings > Members, the list shows each person's name, role, number of teams, and the date they were added. Use the row menu (⋯) to:
- Change role -- the Owner and Admin choices are available only to Owners.
- Remove from organization -- asks for confirmation.
INFO
Removing someone from the organization also removes them from all of its teams. Their history -- to-dos, meeting ratings, issues -- stays intact.
Team Membership
Only members of an organization can be added to its teams. Team membership is managed by organization Owners and Admins in Organization settings > Teams: each team card lists its members and lets you change a member's team role, remove them from the team, or Add to team from the list of organization members.
A person can belong to several teams with a different team role in each -- for example, Owner of the leadership team and Member of the marketing team.
INFO
Removing someone from a team does not affect their organization membership or their other teams. It only removes their access to that team's data.
Team Permissions
What a person can do inside a team depends on their effective team role. Team roles are ordered VIEWER < MEMBER < ADMIN < OWNER -- each role can do everything the roles below it can. Organization Owners, Admins, and Implementers act at least as team Admin in every team of the organization.
| Action | Minimum role |
|---|---|
| Read team data | Viewer |
| Create and edit to-dos, issues, headlines, segue, cascading messages, and document links | Member |
| Enter scorecard values, rate your own meeting (within the rating window), save People Analyzer evaluations (as yourself) | Member |
| Update Rock status and milestones | Rock owner or Admin |
| Manage measurables, Rocks, meetings (create, start/end, record a past meeting, edit time, rate for others, mark absent), the team's V/TO traction (1-Year Plan, archive), and Accountability Chart | Admin |
| See everyone's People Analyzer ratings (the Team view) | Admin |
| Delete anything | Admin |
Implementers have Admin rights in every team, except that they never rate meetings themselves.
The company vision on the V/TO (Core Values, Core Focus, 10-Year Target, Marketing Strategy, 3-Year Picture) is shared by all teams and has its own rule: organization Owners and Admins, Implementers, and the Admins and Owners of a leadership team edit it; everyone else in the organization reads it.
INFO
All permission checks are enforced on the server, not only hidden in the user interface. Actions a user is not allowed to perform are rejected even if they are attempted directly.
Only organization Owners and Admins see the Create Team button.
WARNING
In a suspended organization, everyone can still sign in and read, but nothing can be changed -- see Suspending an Organization.
Time Zone
Each person can choose their own time zone in Settings > Time zone. The default is Organization default (…), which follows the organization's time zone. The list is long, so type a city or region (for example Prague) to find yours.
- Dates and times are shown in your time zone. If you have not set one, the organization's time zone is used, and if that is missing, Europe/Bratislava.
- Calendar dates -- such as to-do due dates and meeting days -- never shift between time zones.
- Meeting start times (for example when recording a past meeting) are entered in your time zone.
API Keys
Each person can create personal API keys in Settings > API keys to connect other tools to EOS Hub through the REST API. A key acts with the person's current roles, so removing someone from an organization or team also ends their keys' access to it. See API Keys.
The Platform Operator
The installation is run by a platform operator (system role SUPERADMIN, shown as Platform admin). The operator creates organizations, suspends or resumes them, and configures AI for the whole platform in Platform administration. The first operator is created by the onboarding wizard; operators appoint further ones in Platform > Users (Make platform admin).
INFO
The platform operator has no automatic access to customer data. They see an organization's teams only if they are also a member of that organization.
When Someone Leaves
Remove them from the organization in Organization settings > Members. They lose access to all of the organization's teams, while Rock ownership, to-do assignments, and meeting history stay intact.
Related Pages
- Organization Settings & Platform -- Managing the organization and the platform
- Roles & Permissions -- What each role can do
- Organizations & Teams -- How organizations and teams work