v1.2 Changelog

Released: October 2026

The "organizations & platform" release: one installation now hosts several companies, each managed by its own Owners and Admins, while the platform operator runs the installation without automatic access to customer data.

Highlights

• Multiple organizations per installation, with an organization switcher in the sidebar
• Organization roles: Owner, Admin, Member, and the new Implementer for external EOS Implementers
• New Organization settings (/org/settings) for people, teams, time zone, and language
• New Platform administration (/platform) for the operator: organizations, accounts, and AI
• Time zones per organization and per user
• AI API keys stored encrypted; database schema managed with Prisma migrations

Features

Organizations

• An installation hosts several organizations. People can belong to several organizations and switch between them with the organization switcher in the sidebar header, which shows the organization's name and your role. Your choice is remembered.
• Opening a team of another organization you belong to switches to that organization automatically.
• Organization roles:
  • Owner / Admin -- manage the organization (settings, people, teams) and act as team Admin in every team of the organization (Owners stay Owner where they are team Owner). Only Owners grant or revoke Owner and Admin; an organization always keeps at least one Owner.
  • Member -- sees and works only in their own teams, with their team role (Owner, Admin, Member, Viewer as before).
  • Implementer -- an external EOS Implementer or coach: acts as team Admin in every team (facilitates meetings, manages Rocks, Scorecard, and more), but does not rate meetings and cannot manage organization settings or people.
• Only members of an organization can be added to its teams. Removing someone from the organization also removes them from its teams; their history (to-dos, ratings, issues) stays.
• People without an organization see a No organization yet page.

See User Management.

Organization Settings

• New page Organization settings (/org/settings) for organization Owners and Admins, with three tabs:
  • General -- organization name, time zone (default Europe/Bratislava), and default language (EN/SK) for new accounts.
  • Members -- name, role, number of teams, date added. Add member by email: an existing account is added directly, otherwise a new account is created that signs in with Google (organization admins never set passwords; email invitations come next). Change role or remove from the row menu, with confirmation.
  • Teams -- create, rename, and delete teams (with confirmation -- deletes all team data), leadership flag, meeting length and warning minute, and team members with their team role.
• The old Admin page (/admin) is gone and redirects to Organization settings.

See Organization Settings & Platform.

Platform Administration

• New page Platform (/platform), only for the platform operator (SUPERADMIN, shown as Platform admin):
  • Organizations -- list with members, teams, creation date, and status; Create organization with name, time zone, default language, and first Owner; Suspend / Resume with confirmation.
  • Users -- all accounts with organization count, role, and creation date.
  • AI -- AI providers and system prompts, now platform-wide instead of per organization.
• The platform operator no longer has automatic access to customer data: they see an organization's teams only if they are also a member of it. An operator without any organization lands on /platform with a platform-only sidebar.
• A suspended organization is read-only: members can sign in and read, a banner says "This organization is suspended — read only", write controls are hidden, and the server refuses changes.

See Platform Administration.

AI

• AI configuration moved from the organization to the platform and is managed by the operator in Platform > AI.
• API keys are stored encrypted (AES-256-GCM) and only ever shown masked. To change a key, enter a new one.
• Planned for a later release: AI credits, using your own API key (BYOAI), and company context.

See AI Integration.

Time Zones

• Each organization has a time zone, and each user can choose their own in Settings > Time zone (default: "Organization default (…)").
• Dates and times are shown in the user's time zone, falling back to the organization's, then Europe/Bratislava.
• Calendar dates (due dates, meeting days) never shift between time zones. Meeting start times are entered in your time zone.

Settings

• New Time zone select.
• Password change now shows errors properly.

Upgrade from v1.1

Back up first

Back up the database before upgrading.

1. Set DATA_ENCRYPTION_KEY. This new environment variable is required: base64 of 32 random bytes, generated with openssl rand -base64 32. It encrypts stored secrets such as AI API keys. In production the server refuses to start if it is missing or invalid. Keep it stable and backed up -- if it is lost, stored API keys become unreadable and must be re-entered. See Configuration.
2. Start the new version. The database schema is now managed with Prisma migrations (prisma/migrations). The Docker entrypoint runs prisma migrate deploy on start, and a database created by the old db push flow is detected and baselined automatically. No manual step is needed. See Database Migrations.

The data migration runs automatically on the first start:

• Every team member becomes a Member of the team's organization.
• Existing superadmins become Owners of every existing organization, so nobody loses access.
• If the installation has exactly one organization, every remaining user without a membership becomes its Member.
• Every organization gets at least one Owner.
• The AI configuration of the first organization becomes the platform AI configuration.

After the upgrade, check Organization settings > Members and adjust organization roles -- for example, make your EOS Implementer an Implementer or promote your team leads to Admin.