TISvia
000
Web · AI · Automation
Web & AI Studio
← Projects

MemberMax

MemberMax is a corporate drive on Drupal 10: folders, role-based access, search and file versions. The logic of Google Drive, the environment owned by the company.

Case
02
Field
Website · File portal
Format
Internal system for the client
Link
Private project
02 — MemberMax

The client cabinet is restricted. Screens show product logic, not their files.

Challenge

Company files lived everywhere: email, messengers, personal drives, USB sticks. The current version of a contract was often “with whoever edited it last”. A new hire did not know where to put a document or who was allowed to see it.

A public cloud “like everyone else” was not an option: they needed their own roles, folders and access policy, and everything had to stay inside the company — not in someone else’s account. At the same time people already knew the Google Drive model, so the product could not feel alien.

Solution

We built a file portal on Drupal 10: a familiar folder tree, drag-and-drop upload, previews, search and rights for who can see, edit or only read.

An admin grants access by department instead of forwarding a zip in chat. Version history leaves a trail: which revision is current and who put it there. The team works like on a drive — but the drive belongs to the company.

How it works

  1. 01

    Structure

    Folders by department and project. A file has one place, not ten copies in a thread.

  2. 02

    Access

    Roles and rights at folder level: a manager sees their own, a contractor sees only what was shared.

  3. 03

    Work

    Upload, preview, comment, a new version on top of the old one — no “final_final_v3”.

  4. 04

    Search

    People find a document by name and content, not by remembering which chat it was sent in.

Features

  • Folders and files in the company hierarchy
  • Access by role and department
  • Document preview without extra software
  • File versions instead of duplicates
  • Search across the vault
  • Drupal 10 admin so the product can grow without a rewrite

Results

  • One drive instead of copies scattered across email and chats
  • Access is granted by rules, not by forwarding a file
  • The team recognises the Drive habit — without putting data on a third-party account

Stack

  • Drupal 10
  • File storage
  • Roles and ACL
  • Search
  • Versioning
Discuss a similar project →
Next caseVVV-Trans →