Kwark. Design System
Open Kwark

Sharing and roles

Sharing in Kwark is one panel, by film role, safe by default. New people are Readers, the request link is off, every person is named and removable, and because Kwark sends no email the owner sends the invite themselves.

Patterns
Who has access
MSMira Sen
Owner
DRDev Rao
Until 30 Dec
✉asha@example.com
Invited · not joined yet

The problem

A writer has finished a draft and wants her director, two actors and a DOP to read it before the table read on Saturday. Before November 2026, Kwark asked her to choose three tabs, a “how they get in” option before she could even type an address, and then 14 modules × 4 levels: 56 buttons in a nested scroll. The default was edit everything. Nobody she invited was ever told, because Kwark sends no email. A person she removed was told the project had been deleted. A declined request could never be asked again. A locked module told collaborators it was “still being built”.

Her screenplay is the most sensitive thing in Kwark. If sharing is confusing she either does not collaborate, or she over-shares by accident. The founder: “the sharing module UX and UI both are very very bad… we are not providing a good user experience to the people who would want to collaborate… not just fix the UI, better user experience, ease of use, and more usefulness.”

Kwark’s answer

Decision 0042: sharing by film role, in one panel, safe by default.

One panel, in the order of what matters

  1. Requests first (someone is waiting): “Asking to join”, with Keep and Decline. Appears only when someone is waiting.
  2. Add people: email addresses, a role, and an optional end date.
  3. Who has access: everyone, each with their role and a ⋯ menu.
  4. The request link, off until turned on.

Roles a producer would name

A role is a template over the per-module map; the map is the authority, and access is never trusted to the label. Roles that behave the same in this copy of the app are not offered twice.

Role What it gives
Reader Reads the screenplay. Nothing else.
Actor Reads the screenplay and characters, and sees the calendar.
Co-writer Writes with you: screenplay, outline, characters, world, research, pitch.
Director Edits the screenplay, story and production. Reads the pitch.
Producer Runs production: cast and crew, calendar and pitch. Reads the story.
Camera Shapes the look and the shots. Reads the screenplay and production office.
Crew Reads the screenplay, production pages and the calendar.
Custom Any module-by-module change turns the label into Custom.

Underneath, Module by module… gives the fine-tune: each module is No access, Can read or Can edit. Screenplay covers every draft and episode; Research keeps personal notes private; Cast and crew includes contact details; Production office is one permission today (breakdown, shots, schedule, call sheets, budget, paperwork, departments), and splitting it so an actor can see call sheets without the budget is the first follow-up.

Safe defaults

  • New people are Readers.
  • The request link is off. When on, it offers a role and every person who asks is approved by the owner: “The link is on. You approve everyone who asks.” / “The link is off. Nobody can ask through it.”
  • Sharing works through Google accounts, so only the people you add can open it.

Kwark sends no email, so it says so

After inviting, the panel offers Copy invite message and Email the invite (the owner’s own mail app). The message:

{Owner} has shared “{title}” with you on Kwark, as {Role}. Open it here: {link}. Sign in with the Google account for {email}. Kwark only lets that address in.

Copying says “Copied. Paste it into WhatsApp or an email.” Invites point to /invited/{project}, which tells the person which Google account to use and who invited them, as what, before they sign in.

Per person (⋯)

Module by module…, Set an end date…, Parts they read…, Draft they see…, Named on project page, Copy invite message, Email the invite, and Remove access (confirmed). “Draft they see” is a view preference, not a security boundary, and the panel says so.

On the collaborator’s side

  • Permission changes arrive live.
  • A module not shared with them: “{Owner} hasn’t shared {module} with you.” / “Ask {Owner} if you need it.” Locked and hidden merged into one No access; neither was readable, and a lock tile only invited a question nobody could answer.
  • When access ends, a named page: “Your access has ended”, “Your access to {project} ended on {date}.”, “You left this project”, with Go to your projects. Never “the project has been deleted”.
  • Leave project is always available to them.

Anatomy

Element Means
Requests box (accent outline) People waiting; the count is how many
Role button (word and chevron) Opens the role menu; the word is the current role
Dashed envelope avatar Invited, has not signed in yet (“Invited · not joined yet”)
“Until 30 Dec” Access ends after that day
“Access ended …” Dims the row
Request link Off or On Whether anyone with the link may ask to join
Bell bubble number (accent) People asking to join, across your projects; it never pulses

Rules

  • Must default new people to Reader and the request link to off.
  • Must check access against the per-module map, never the role label.
  • Must say plainly that Kwark sends no email, and give Copy invite message and Email the invite.
  • Must name every person with access and make each removable, with a confirm that says what they keep.
  • Must show a collaborator a named “access ended” page and a calm “hasn’t shared” page, never a deletion message or “still being built”.
  • Never let anyone in by link alone; the owner approves every request.
  • Never offer a role that behaves the same as another in this copy of the app.
  • Never let a collaborator create edit access for another account. (The old rules allowed it; the rewritten rules on feat/sharing-rebuild close it and are not deployed without the founder.)
  • Always put waiting requests first.
  • Always make one change one batch, and say so if it fails: “That change was not saved. Try again.” A failure must never look like “nobody has access”.

Edge cases

  • The owner types their own address: “That is your own address. You already own this project.”
  • A date in the past: “Choose a date after today, or choose No end date.”
  • Wrong Google account at the invite: the join page names the address the invite was for.
  • Declined request: the person may ask again later; a decline is not permanent.
  • A new link: Make a new link? retires the old one; “A new link is ready.”
  • Browser blocks copying: “Your browser blocked copying. Select the text and copy it yourself.”
  • Not signed in: the panel shows Sign in to share and why: sharing works through Google accounts.

Phone and desktop

On a phone the panel is full screen with the one-line header (“Share”) and one scroll; each person’s ⋯ opens a sheet that drills into Module by module one page at a time. On desktop it is a single dialog with one scroll, never nested scroll areas. Every control is a word, reachable by keyboard.

Accessibility

  • The role button’s accessible name includes the person: “Dev Rao’s role: Director”.
  • The requests box is a region with a heading and a count in words.
  • Module levels are a radio group per module with a legend naming the module.
  • The dashed envelope avatar has a text equivalent: “Invited, not joined yet”.

Add “dev@example.com” as Reader (the default), then Copy invite message and paste it into WhatsApp.

Do

Add “dev@example.com” with edit access to every module by default and show “Invitation sent” when nothing was sent.

Don’t

“Mira hasn’t shared Budget with you. Ask Mira if you need it.”

Do

A lock icon and “This module is still being built.”

Don’t

Demo

Asking to join
AKAsha Kumar
asha@example.com · asks as Actor
Add people
Kwark doesn't send emails. Let them know, and say which Google account to use.
<div class="kw-card" style="width:100%;max-width:520px;display:grid;gap:10px;border-color:var(--k-accent)"><strong>Asking to join</strong><div class="kw-row"><span class="kw-avatar" style="--kw-peer:var(--k-brand-aqua)">AK</span><span class="kw-row__title">Asha Kumar<br><span class="kw-row__meta">asha@example.com · asks as Actor</span></span><button class="kw-button kw-button--sm" type="button">Decline</button><button class="kw-button kw-button--sm kw-button--primary" type="button">Keep</button></div></div>
<div class="kw-card" style="width:100%;max-width:520px;display:grid;gap:10px">
<strong>Add people</strong>
<div style="display:flex;gap:8px;flex-wrap:wrap"><input class="kw-input" style="flex:1;min-width:200px" placeholder="Add people by email" aria-label="Email addresses to invite"><button class="kw-text-button" type="button" aria-label="Role for the people you add">Reader <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><path d="m6 9 6 6 6-6"/></svg></button><button class="kw-button kw-button--primary" type="button">Add</button></div>
<span class="kw-hint">Kwark doesn't send emails. Let them know, and say which Google account to use.</span>
</div>
<div class="kw-menu" role="menu" aria-label="Role" style="width:320px"><button class="kw-menu-item" role="menuitemradio" aria-checked="true" type="button">Reader <kbd>✓</kbd></button><button class="kw-menu-item" role="menuitemradio" aria-checked="false" type="button">Actor</button><button class="kw-menu-item" role="menuitemradio" aria-checked="false" type="button">Co-writer</button><button class="kw-menu-item" role="menuitemradio" aria-checked="false" type="button">Director</button><button class="kw-menu-item" role="menuitemradio" aria-checked="false" type="button">Producer</button><button class="kw-menu-item" role="menuitemradio" aria-checked="false" type="button">Camera</button><button class="kw-menu-item" role="menuitemradio" aria-checked="false" type="button">Crew</button><div class="kw-menu-sep" role="separator"></div><button class="kw-menu-item" role="menuitem" type="button">Module by module…</button></div>
<label class="kw-switch"><input type="checkbox" role="switch"><span class="kw-track"></span>Anyone with the link can ask to join</label>

Avatar, Menu, Copy field, Destructive actions, Collaboration, Notifications.

AI readiness test

Task. Let an actor see call sheets without seeing the budget.

Give the agent. This page, Decision 0042, utils/shareRoles.ts, never-test-rules-on-live-project.

Constraint. No rules deploy without the founder.

A reliable answer

  • Splits the Production office permission in the module map, not in the role label
  • Updates the Actor template to read call sheets only
  • Makes production pages cope with partial data
  • Plans rules in the emulator and asks before deploying
  • The collaborator sees “hasn’t shared Budget with you” for the rest

Give this Markdown to your coding agent or share its URL.

Open .mdllms.txt
Loading…