Organizations in MMW

An organization is a shared memory space for a company: units, people with their own keys, and rules for who sees which records. Knowledge an employee adds while working with agents belongs to the organization and stays there when the person leaves.

On this page you will learn:

1. how an organization differs from your personal space;
2. what the company gets;
3. how to create an organization and get it activated.

Example used throughout this section: Northwind (a legal entity) has an Engineering department with a Backend unit and a Platform team inside. Anna heads Backend, Ben is a member of Backend, and Vera is a contractor hired for two months.

Personal space and organization

Everyone has one login and one personal space. On top of that, a person can belong to any number of organizations. The “Space” switcher in the account sidebar lets you pick “Personal” or an organization.

	Personal space	Organization
Who sees records	Every key of the space sees all of its records	Each person sees only what a record’s visibility allows
Keys	Your keys	Each member issues their own key
Structure	Projects and workspaces	Unit tree, roles, projects
When someone leaves	—	Their knowledge is handed to a chosen recipient
Billing	Personal plan	Seats in the organization

Note

An organization never becomes your default space. A key issued in your personal space works only with personal memory; a key issued in an organization works only with that organization’s memory. The organization has no access to an employee’s personal space.

What the company gets

Structure and roles

Holding, legal entity, branch, department, unit, team. Roles: admin, head, member, contractor, auditor.

Record visibility

Author-only draft, unit, project or the whole organization. Enforced by the server on every read path.

Knowledge handover on offboarding

Keys are revoked at once, and a chosen person receives all of the departing employee’s records, drafts included.

Time-limited contractors

Access for 1 to 365 days closes by itself; after it ends the seat is no longer billed.

Audit log

Offboarding, reads of handed-over knowledge, visibility and access-term changes — without memory content.

Per-seat pricing

$18 per seat per month, $14 when paid yearly, minimum 5 seats.

How it fits together

  One login (email)
        │
        ├── Personal space ──── personal keys ──── personal memory
        │
        └── Organization "Northwind"
              ├── Engineering (department)
              │     ├── Backend (unit, head: Anna)
              │     │     member Ben, contractor Vera
              │     └── Platform (team)
              └── ...
              each person has their own key → the agent sees only permitted records

Getting started

1. Sign in at app.mmwhub.tech and verify your email if you have not yet. Without a verified email you cannot accept an invitation; you can request the email again with “Send the email again” on the Organizations page.

2. Open Organizations → “Create organization”. Enter a name (up to 120 characters) and, optionally, a tax ID of 10 or 12 digits. You become the admin, and the name becomes the root node of the structure, of type “Legal entity”.

3. On the Structure tab, add departments, units and teams. See Structure and roles.

4. Email support@mmwhub.tech to enable a pilot or activate the organization. The pilot lasts 14 days for up to 10 seats. For now the MMW team activates organizations manually; there is no self-service card payment for organizations in the account.

5. Invite people on the People tab and ask each of them to issue their own key on the Keys tab. See Invitations and keys.

Caution

Before activation, people can sign in, accept invitations and issue keys, but their agents are refused: organization memory is unavailable without an active subscription. The Keys tab then shows “To let people connect agents, the organization must be activated”.

Not available yet

• SSO/SAML sign-in;
• invitation emails: the admin passes the link on;
• self-service payment for organizations;
• sharing records between legal entities within a holding;
• importing people from directory services.

Next steps

Structure and roles Unit types and exactly what each role can do.

Record visibility Who sees which records and where that is checked.

Invitations and keys Add a person and connect their agent.

Organization billing Seat price, who takes a seat, the pilot.