Team edition

The Team edition brings several people together to share a single company configuration while keeping whoever governs the baseline separate from whoever contributes memories. To do this it uses two repositories and derives roles directly from your git account’s permissions — there’s nothing to configure in the app.

Two repositories, two write roles

Team setup configures two repositories because governance separates managed configuration from memories:

• CORE — governed configuration. It’s the company baseline: rules, skills, commands, agents. Maintainers write it; members receive it read-only.
• MEMORIES — team memories. It contains project memory, the seat registry, and audit. Everyone contributes, including those who are read-only on CORE.

A single wizard configures both: with the same provider and the same organization, one authentication is enough.

Why two repositories

Separating CORE and MEMORIES is what lets a company keep a consistent, controlled configuration (only maintainers change it) without preventing every member from accumulating and sharing their own project memory.

Roles and permissions

The role isn’t configured in the app: it’s derived from your account’s permissions on the git repository. Whoever can write to CORE is a maintainer; whoever can only read it is a member.

Role	CORE	MEMORIES	What they can do
Maintainer	write	write	Manages the company baseline and plugins, generates invites, performs repository maintenance, can deactivate machines and merge projects.
Member	read	write	Receives the configuration and contributes memories. In roster views, others’ data is masked.
Viewer	read	read	Read-only view.

Tip

Want to promote or demote someone? Change their permissions on the git repository: at the next sync, the role in the app aligns itself.

Team defaults

The maintainer’s choices become the team defaults: settings such as the automatic-sync cadence and the memory options are propagated to the other members, who inherit them automatically at the next sync. It’s how the whole team gets a consistent configuration without everyone setting it up by hand.

Inheritance never overwrites your explicit choices: if you’ve already set one of those options yourself, your preference stays. Team defaults only fill in what you haven’t decided yet. So a new machine starts out aligned with the team, while anyone with particular needs keeps their own control.

Deleting and reviving shared items

When a maintainer deletes a shared item — a skill, rule, command, agent, hook, or custom plugin — the deletion reaches the whole team at the next sync and stays deleted: a member’s machine that was behind no longer brings it back. Members don’t have to do anything; the item simply disappears and doesn’t return.

A maintainer can bring a removed name back with Revive, shown in a Deleted by the team list at the bottom of each section. Revive re-allows the name so the item can be created and shared again — it does not restore the previous content (recover that from git history or a backup).

Joining a team

If you received an invite code — it starts with KNMI- — it takes only a few steps: in one go you activate the team license and configure the repositories with your personal git credentials.

1. Paste the code into the showcase.

   In the Already have a license? panel, paste the KNMI-… code into the Paste your license code field and click Activate. The code is recognized as an invite and the Join the team modal opens.

2. Enter your git details.

   In the modal, fill in Your name, Email (for commit attribution), Username, and Access token for your personal git account. The modal doesn’t close if you click outside, so you won’t lose what you’ve typed.

3. Click Join.

   In a single step the team license is activated and the two repositories (CORE and MEMORIES) are configured with your credentials. From here you continue with the normal sync cycle.

Caution

Invite codes are never stored: once you’ve used a code, keep a copy only if you expect to need it again before it expires. A maintainer can always generate a new one.

The Team tab

With the Team edition, the dashboard shows a dedicated Team tab.

• Your identity. If this machine has no identity yet, a card asks for your name and email and saves them. The email is what lets your git host attribute the sync commits to you — without it they stay anonymous. You can change both later from the User settings panel.
• Members. The list of members with their respective machines and role (Maintainer / Member / Viewer ).
• Generated invites. A table with date, author, expiration, and status of each invite (pending, redeemed, expired).

Generating an invite code

Maintainer

From the Team tab, Generate invite code creates a code to share. You can copy it, send it by email, and it’s assigned an expiration. Remember that the code isn’t retained by the app: share it with the invited person right away.

Member / Viewer

Generating invites is reserved for maintainers. If you need a code for a new colleague, ask a team maintainer for one.

See also

• First launch and setup — license activation and connecting the repositories.
• What it syncs — the sync domains, team governance included.
• Repository maintenance — safe operations on CORE and MEMORIES.