Sharing a project
People come into a project in one of two ways. You invite people by name — to view it, or to make it with you as a collaborator. You publish it for everyone to view: a viewer opens the link of a published project, or finds it in Explore (see "Publishing", below), and needs no invitation.
Inviting people
Open the project's ⚙ menu and choose Invite people, then give their handle (@luo or just luo) or their email address, and choose what the invitation gives: Viewer — can view, or Collaborator — can edit. Viewer is chosen until you change it; a collaborator's asks run on your project and your usage, so give that to someone you would trust with it. A project shared with you says who shared it — "shared by @luo".
Someone without a Kuyun account. Kuyun is in a private beta, so an email address with no account does not get in straight away. The address joins the waiting list with a note that you shared this project with them, and they get an email saying so, once for each project: never twice for the same project, even if you withdraw it and share it again. They are not in the signup queue because you shared: they join it when they sign up themselves. The people running Kuyun see your note and may let them in sooner. When they are let in, your invitation is waiting for them to accept. Until then your list of people shows them as waiting to join Kuyun, and you can withdraw it like any invitation; deleting the project withdraws it too. You can send up to ten such emails a day.
A project you work on as a contributor is on the Create page, under "Shared with you"; one you view is on your Shelf (Shelf).
The two kinds of access
- Viewer — someone its owner invited to view it, or who opened a published project's link or started it from Explore. They get what is in the project's Output folder and nothing else: what the project delivers. They see it as the files themselves, at the top of their list, with no Output folder around them. That is its README (what is there and how to use it), every part of the work as it is delivered (a course's lessons and practice, a book's chapters, a briefing's daily digests), any trip map, the tables in its Output (never the working tables Kuyun keeps while making it), and the files you chose to share with them — and their own conversation about it, which reads those same files and can look things up in the tables for them. Their page is that conversation with those files beside it; a chapter opens in the reader (Studying with a project); a table opens as its rows — never who changed them or their history, and on a personal project not where the values came from either. A viewer pays for their own viewer chat in tokens (Tokens). They do not see the goal, the brief, the plan, the findings, the web pages Kuyun collected or any file you did not put in Output, their chat is told nothing of how the work is made, and they cannot change anything. A viewer downloads nothing: no file, recording, table or copy of the work. They read, listen and practise on Kuyun, where a recording plays and offers no save; the people who make the project keep every download. When the people who make it delete a part, it leaves the viewer's list, and the viewer's place and progress on that part go with it.
- Contributor — they get the whole workspace: goal and context, the brief, the plan, findings, resources, the Output folder, and the project's Creation Console, where they can add context and answer questions alongside you. Like you, they can upload files and choose which go into Output for viewers, and edit or delete what is in Output. They can ask the chat to change the brief, which changes what the work is judged against — so invite someone you would trust to redraw the goal. A contributor can also make a COPY of the project for themselves — its work and its files, but not its people, its conversations, or what only you see — which is then theirs (see Renaming, copying, archiving and deleting a project).
You invite a viewer or a contributor by name; publishing gives everyone a viewer's access without an invitation.
What the other person sees
A person you invite gets an invitation, which they accept or decline. Nothing is shared until they accept.
They see that project and nothing else. Sharing a project does not give anyone access to your other projects, your files, your other conversations, or anything Kuyun knows about you personally.
If the project is generic, the person you shared it with may also link it into a project of their OWN, which can then ask it questions — and get the answers a viewer would get, nothing more. You are not shown what they ask; their questions and its answers are kept with their project, not yours — so anyone THEY share that project with may see those answers too. A personal project can never be linked by anyone but you.
What they do not see
Your memory. What Kuyun knows about you — your situation, your preferences, your history — is not shown to someone you share a project with. What was written before you shared is the one exception, below.
From the moment you send an invitation, the whole project works the way a generic project does — its research, its chat, your own conversation with it included, and its Ask box. It works from its own material and the open web, never from what Kuyun knows about you, and nothing it has learned about the people you share it with is brought in either. This lasts while any invitation or share is open; once the last one is declined or removed, the project is yours alone again.
The one thing this cannot undo is what was written BEFORE you shared it — or while it was yours alone again. Findings and text written then may reflect what Kuyun knew about you, and the people you share it with can read them. The material gathered from your own pages and documents for its research is no longer used once it is shared, and is never shown to anyone but you.
Taking it back
You can remove someone's access at any time. What they contributed while they had access stays in the project; their ability to reach it stops. Their own record in it goes with their access — where they were, what they finished, the answers they typed in its practice — so a person you remove leaves nothing of theirs behind, as when they remove it themselves. A copy a contributor made while they had access is theirs and stays with them: removing their access, or deleting the project, does not take it back.
There is a second way access ends, and it does not work the same way. If the owner DELETES the project, it is gone for everyone in it — not just your way in, but your side of the conversation with it, and anything spoken in it. Revoking takes back the key; deleting takes down the house. (Answers it already gave to another project that asked it stay in that other project, where they were asked.) A course you were studying can end that way, and a viewer downloads nothing, so what you studied there stays only as long as the project does.
A work on a library's shelf. A library can shelve other works — its owner's, or any work on Explore. Its viewers see a shelved work only while that work is published, and see of it exactly what its own viewers see — a course's lessons open for them as they finish them, when its maker locked them; unpublish a work and it leaves every shelf at once. The library's owner sees the work's card on their own page and opens the work itself to read it. Reading a chapter of a shelved work through a library counts as reading that work, for its own maker.
Publishing
Publishing is how a project gets viewers. A generic project with at least one unit filed — a course, say — can be published; a personal one cannot, because its work may carry what Kuyun knows about you, and that is never shown to a stranger — so a personal project gains no new viewers at all. Only its owner can publish it.
Open the project's ⚙ menu and choose Publish. It is four short steps: what publishing gives; the title and the tagline; the picture; and a look at the whole cover (below) as a stranger will see it. Then one press publishes: the project goes into Explore for everyone signed in and onto the works page the sign-in page points to, where anyone can find it, and Kuyun gives you a link to post wherever your people are — on social media, in a message, on a page. Where the link is pasted it unfurls into the cover: its picture, its title and its one-line promise. Your name is on it the way it is on a shared project — your handle, nothing else.
Locking what a viewer has not finished. On a course or a role-play practice, the first step of Publish has a box: Lock what a viewer has not finished yet. On a course it starts unticked, so every lesson is open to your viewers from the start. On a role-play practice it starts ticked, because a scenario's file is mostly the answers. Ticked, each lesson or scenario — with its practice and the answers — opens to a viewer only once they have worked through it with their study partner. What they have finished stays open, and one they are partway through locks again. It is kept as you tick or untick it, published or not, and takes effect the next time a viewer opens the work. You and your collaborators always see everything.
Its own page, open to the web. The link is a page anyone can read without signing in: the cover, your handle, the opening of your introduction and the titles of the chapters or lessons — never a chapter's text, which stays for viewers. The same page is what search engines read, so a work can be found by searching the web for what it teaches, and Kuyun keeps a map of every published work for them, with the works page and its collections — Read aloud, Courses, For children and the other topics Explore shows. When you publish or unpublish, Kuyun also tells the search engines that take such a notice (Bing, and the ones that share its index) that the page changed, so it is found — or forgotten — sooner. A work that was only ever reached by its link, from before every published work was listed, was never in the map, so unpublishing it tells them nothing. Someone who finds the page is offered one button, Start free — sign in or sign up — and their account opens on your work; someone already signed in is taken straight into it. Unpublish, and the page and its place in the map go at once — but a search engine may keep its title and one line in its results for days or weeks before it notices.
The cover. Everything that offers your project to a stranger — a card in Explore or on the works page, the head of its public page, a posted link's preview — shows the same three things: a title, a tagline saying what someone will be able to do after it, and a picture. Kuyun writes the tagline and a short description of the picture from the README and the first lessons, in the project's own language. The title is always the project's own name: the words step shows it, but you cannot change it in Publish. To publish under another title, rename the project: click its name at the top of the project page, and the published work, its cards and its link take the new name. The tagline is in a roomy box to edit, with Generate tagline, above it, for a new one. Two more things are written when you press Publish, and they are Kuyun's rather than yours: the opening, two or three sentences a viewer reads first when they open the work, at the top of its conversation, and the search words Explore uses to find and recommend it — the subject and other words for it in English, Chinese and Spanish, and who it is for (Explore). Neither is shown in Publish or can be edited: Kuyun writes them from the work as it stands when you press Publish, from the project's name, the tagline and the work itself, and writes them again each time you publish, so they always match the name and the tagline you published under. A viewer sees the opening when they open the work; to change what it says, rename the project, change the tagline or the work, and publish again. A work published before these existed starts its viewers with its README's first lines until it is published again; its search words Kuyun writes by itself, at no cost to you, within a few minutes of noticing it has none. The picture step shows the picture's description first — a scene from the work itself in a hundred words at most, never a generic study picture — for you to change; Generate picture from text, right below it, draws from it, with no lettering in it, as often as you like. Upload a photo, beside it, uses a picture of your own instead: a JPEG, PNG or WebP of up to 15 MB, at least 600 by 400 once cut to shape. Kuyun turns it the right way up, cuts it to three by two about its centre, makes it 1200 by 800, and removes what the camera wrote into it — where it was taken included — since a cover is public. An uploaded photo costs no tokens. The picture is drawn wide, three by two, and shown whole at that shape everywhere — the cards, the public page, a posted link's preview — so nothing of it is cut off. Accept shows the whole cover as the very card Explore will show, then Publish keeps the cover, publishes the project and shows its link, with Copy link to put it on your clipboard for posting, Open it to see it as others will, and Done to dismiss it. A published project walks the same steps to update its cover, ending in Save the cover, which closes it too. It costs your tokens, as a picture in a lesson does (Tokens), and takes about half a minute. Accept waits for a picture: a cover is published with one, so until it has one — drawn or your own photo — Accept stays greyed out and says so. If no picture can be drawn, the words stand; try again, or upload a photo.
The cover lives in your project's Files, in a folder called Cover, beside Output: cover.yaml holds the tagline, which you can edit there like any file and save, and the picture sits beside it. It has no title: the title is the project's name, changed by renaming the project. The file also shows the opening and the search words Kuyun wrote for Publish, so you can see them, but they are Kuyun's: a change to those two lines is not kept. Viewers never see the folder; the public page and the cards read from it.
Nothing changes the cover on its own: a new lesson or a rewritten README leaves it as you approved it, so a link you posted keeps its picture. When you want a new one, open Publish again, or ask the producer in the project's chat — "make the cover about the counting lesson", "a new picture, a lantern at dusk" — and it remakes it to your words, at your cost. On a work you published before covers existed, Publish offers to make one; until then its cards show the coloured tile and its README's first lines.
- Someone signed in who opens the link becomes a viewer of the whole project at once — no invitation, nothing to accept. The link IS the work's page for them (Shelf, "A work's own page"), and it is on their Shelf from then on. You opening your own link see it the way a viewer does.
- Someone without an account sees the project's public page: its cover, who made it, the opening of its README and the titles of its units — never a unit itself, and no conversation. Kuyun makes that page when you publish and keeps it in step with what it shows: change the cover's words, rename or remove a unit, or change your public name, and the page says so the next time anyone opens it. From it they can sign in, or sign up — on the sign-up page, which names your project — and their email joins the signup queue; when their account opens, the project is started for them as if they had opened the link signed in. That spends none of your ten emails a day.
Your viewers can pass the link on. On a published work's own page, a viewer has 🔗 Share: on a phone it opens the phone's own share sheet, and elsewhere it copies the link. It is the same link you posted, and it says nothing about who shared it. Anyone who opens it gets what is described above. A project you shared with someone privately, without publishing it, has no Share for them: its link would open nothing for anyone else, so passing it on is yours to do, by inviting them. An archived work has none either.
A project you published earlier by its link alone, when publishing offered that, stays reachable by its link alone until you open Publish again and press Publish again — nobody listed it on your behalf.
What publishing earns you. A published project can earn its owner earned credit, in money, as people use it on Kuyun. How much a work earns, and from what use, is Kuyun's to set and may change. Earned credit pays for your own work once your day's allowance is gone, like promotional credit, and Settings → Usage lists what each published work has earned you; while a work is published, the producer says it too when you ask what it earned. Turning earned credit into money is on the roadmap and not built yet (Tokens, "Earned credit").
What you see of the people viewing it: never who. Kuyun does not list them or show a count of them on their own; deleting the project counts them among the people who would lose it. Their handles, their conversations and their progress are not shown to you, and a note one of them sends you arrives from "a viewer". Inviting someone — to view it or to work on it with you — tells you nothing either way: whether or not they already view it, they get your invitation the same way and your list shows it the same way. The people you invited by name are listed by name, as a viewer or a collaborator, and you can remove them at any time.
Unpublish is the same menu, and the link stops working at once for anyone new; the people already viewing it keep it until they remove it. Deleting the project closes it for good. While a project is archived it is not in Explore (it leaves at once) and its link says there is no such project; reopening it lists it and opens the link again, because your choice stands until you unpublish — and you can unpublish while it is archived. One exception: a viewer can report a published work (Explore, "Reporting a work"), and if the people running Kuyun decide it breaks the terms they take it off Explore themselves. You are told why, under Publish, and cannot publish it again until they allow it; the people already viewing it keep it, as after your own unpublish.
Removing a project you view
If you view a project — one you opened from its link or Explore, or one its owner invited you to — you can remove it yourself, and everything you did in it goes with it: open the project, then ⚙ → Remove this project. You are asked first, because it cannot be undone. Deleted for good are your conversation with it (and any voice recordings in it), where you were in it, where you stopped reading and where you stopped listening to its narrations, what you finished, the level a placement found for you, your practice answers and scores, any reminder you set for it, how you asked to be answered in that chat, the notes you sent to the people who made it that nobody has answered yet, whether its daily briefings come to your Home chat, and Kuyun's own notes of that conversation. Briefings it already put in your Home chat stay there: they are yours. The owner keeps their project exactly as it was; they cannot see what you did there either way — only the notes you chose to send them, and the practice answers you said were right, which never carried your name. An answer they agreed with and added stays in the course.
Notes from viewers. A viewer can send the people who made a project a note about the work — a mistake, something unclear, the pace — by pressing Send on it (Studying with a project). It reaches the owner and every contributor — with the @handle of a viewer you invited, or as "a viewer" from someone who came by its link or Explore — and nothing else of the viewer's conversation comes with it. The project's chat lists the notes not yet done, offers a fix for each, and answers the viewer when you tell it to.
If its owner invited you, it stays shared with you: you are taken to its invitation, and accepting it again gives you a clean start — the first lesson, nothing finished. If you came by its link or Explore, nothing is left behind, and opening it again starts it afresh. What Kuyun has learned about you in general from talking with you, the way it learns from any conversation, is not picked out and removed (see "What a project may draw on" in The project page). A contributor cannot do this: what a contributor made belongs to the project.
A thing worth knowing
Everyone in a shared project sees the WORK — a viewer what it produces, the files in its Output folder; a contributor that and the documents that make it — but each person's conversation with it is their own. Nobody, the owner included, can read or join anyone else's. Which models serve the project — the one that answers in that conversation included — are the owner's choice: if the owner is an administrator, they may have chosen different ones from the default (see The AI models behind Kuyun).