Working together as a team
One body of knowledge for several people. What one person files, the next finds again in their own AI tool — even once the first has left the company.
The costliest loss in knowledge work is the quiet one: someone resigns, and a project's memory leaves with them. Notes sit in personal chat histories, the reasoning behind decisions is written down nowhere, and whoever takes over starts from zero. A shared workspace solves that, because the knowledge belongs to the team rather than to an account.
What one person files, the next finds in their own tool
The Team plan includes five seats, Business ten. All members work on the same body of knowledge, but each person stays in their own tool: one colleague in Claude, another in Cursor, a third through the browser interface. What is saved in Claude in the morning is found by someone else through ChatGPT in the afternoon.
Everyone sees exactly what they are meant to see
Owner, admin, member and reader. The owner is fixed; the remaining roles you assign per person and change whenever you like. A reader researches the body of knowledge without changing it — useful for working students, external auditors or management.
Whoever leaves the team loses access immediately
You invite by email, invitees sign in with their login link and are in the workspace at once. When someone is removed, the block takes effect immediately: that person's access tokens lose their validity and an open session ends within a minute.
As the team grows, you add seats without asking anyone
When the team grows, you add further seats yourself for 15 euros per person and month. No call, no quote, no waiting.
Who had access when can be documented
Invitations, role changes and removals appear in the workspace audit log. When the question comes up of who had access at what point, there is a dated answer.
Your application signs users in without handing out tokens
From the Team plan on you can register your own OAuth applications. Users of your application sign in against knowmind through it, so you do not have to hand out and collect personal tokens.
Technical detail
- Tenant separation anchored in the database, not in application logic
- Separation applies throughout, including graph and vector search
- Team functionality additionally reviewed against attack assumptions
- Five seats on Team, ten on Business, more can be added
- Article 28 GDPR data processing agreement from the Team plan on