2026

ARCHKIRS Project Workspace

Protected workspace for client collaboration

Case study by Ian Kirs · ARCHKIRS

Web Development
Automation

Project overview in ARCHKIRS Project Workspace

About the project

ARCHKIRS Project Workspace is a separate protected web application for collaboration with clients on specific projects. It gives the owner and client a shared project context without exposing the internal administrative or financial workspace.

The client sees a clear project structure, current conversation, participants, and the available Preview. Communication can happen in Russian, Serbian, or English: original messages are preserved while translations are stored separately and remain auditable.

Inside a Review, Repository AI can use confirmed facts and an immutable repository snapshot to answer verifiable questions about the current project version. Decisions about price, deadlines, scope, and project acceptance remain with the owner. The Workspace is designed for project discussion and working confirmation and does not replace legal signature or formal contract acceptance.

Challenge

Replace scattered email and messenger threads with one calm workspace where a client understands the project state, sees the correct website version, and discusses it without gaining access to other projects or the owner's internal data.

Solution

The Workspace is organized around a specific project and its participants. Owner and client use separate access flows, authorization is verified server-side and through Supabase RLS, and each client sees only their own project context and active Review. Conversation, translations, files, and notifications are stored as separate auditable data. For questions about the current version, Repository AI operates only inside a fixed snapshot and evidence boundary and does not replace owner decisions.

What was implemented

01
Separate owner and client access, passwordless invitations and email OTP, reviewer / viewer roles, multiple representatives, and multiple projects.
02
Project-centered Overview / Chat / Participants interface with project status, Preview, participants, and separate discussions.
03
Multilingual RU / SR / EN conversation: original messages remain unchanged, translations are stored separately, and translation failure does not block communication.
04
Protected attachments with server authorization, quotas, lifecycle cleanup, and protected file delivery.
05
Persistent unread state and notifications with safe deep links that return the user to the exact project and discussion after normal authentication.
06
Server-only AI for translation, dialogue, summaries, and transcription with output validation, audit records, and bounded trusted write operations.
07
Repository AI uses confirmed facts, an immutable snapshot, and evidence controls for answers about the current project without turning retrieval failure into an invented answer or unnecessary owner escalation.
08
Each new website version can use a new immutable Review snapshot without rewriting the history of an existing discussion.

Gallery

Project discussions list in ARCHKIRS Project Workspace — Separate discussions keep conversations organized by participant, task, and review stage.

Discussion workspace with messages and files in ARCHKIRS Project Workspace — A single discussion keeps client and owner comments, files, and clarifications about the current project version together.

Project participants and access roles in ARCHKIRS Project Workspace — Participants manages project access and separates people who join discussions from those who only view the project.

Secure sign-in to ARCHKIRS Project Workspace with a one-time code — Client access is protected by a dedicated private sign-in flow and a one-time code delivered by email.

Business value

The client works in one clear place instead of following email chains, links, and messages across several services.
Owner and client can work in different languages while original messages and translation history remain preserved.
Routine factual questions about the current project version can be answered from confirmed facts and repository evidence without unnecessary handoff, while real commercial and project decisions still remain with the owner.
Project data, files, and discussions are isolated by project and participant, and access can be revoked without relying on a permanent secret link.
This architecture can serve as a foundation for a client portal in a studio, agency, or service business that needs project visibility, structured discussion, and controlled access.

What this system deliberately does not do

A client does not gain access to other projects, the owner's internal admin area, or financial workspace; access is limited to their own project context and active Review.
Repository AI does not operate outside the fixed snapshot and evidence boundary and does not decide price, deadlines, scope, or project acceptance.
The Workspace does not replace legal signature or formal contract acceptance; it is designed for project discussion and working confirmation.

Technologies

Next.js · React · TypeScript · Supabase · OpenAI

View site

Need a similar system?

If you need more than a website - a connected work tool, client portal, or automation for a specific process - tell me about the task. We can start with a focused part and expand the system gradually.