Working together
Talk with your team in an organization's threads and projects, tag @june when you want June, and know whose plan and connections each reply uses.
An organization's threads are shared rooms: members talk to each other there, and June answers only when someone tags it with @june, or asks it afterwards with Ask @June directly.
Every member reads everything in the organization's threads and projects, including what June found through one member's mail or files. Invite only people who may see that (Invite people).
Start a chat in an organization
Filter the sidebar to the organization (or one of its projects) and start a new chat: it is created there. Every member of the organization can read it; a member joins the thread the first time they write in it.
Who wrote what
In the mobile app, your own messages sit on the right. Other members' messages sit on the left with their picture, or their initial when they have none, and their name over the first of several in a row. June's replies carry its flame. A chat that is only yours looks as before.
Ask June
Write @june anywhere in your message. Without the tag, the message goes to the other members and June stays quiet, which the composer reminds you of: "Type a message. June replies when tagged."
@june summarize what we agreed in this thread and list who owns each next step
@june draft the reply to Dana about invoice 1042, using the numbers above
The tag has to stand on its own. An email address such as june@acme.com, a longer word such as @junebug, and anything inside code or a quoted line do not count.
While your message tags June, the send button shows June's flame and reads "Send to June", on the web and in the mobile app. If you sent it without the tag, a notice above the composer reads "This is a multi-player chat." and offers Ask @June directly. The notice stays for 15 minutes after you send, or until someone else writes. Send another message and it offers that one instead; its × closes it. Choose Ask @June directly and @June is added to the end of your message, as if you had tagged June, and June answers.
Whose reply it is
June answers each tag as the member who wrote it, whoever started the thread: with their connections, the model they picked, and their plan unless the organization has a funding source. Whose sign-in June uses has the full rules.
Steer a reply someone else asked for
While June is writing a reply, any member can steer it with a message that tags @june. From that message on, the reply carries on as the member who steered. A message without the tag goes to the members and does not steer.
Tag a member
Type @ and pick a name. The list shows June first, then the organization's members; a member who has not written or been tagged in this thread yet is marked "not in this thread". Picking a name writes @Name into your message; picking June writes @june. A name you type without picking it from the list is not a tag. You can tag up to 32 people in one message.
In the mobile app the list opens above the composer, in an organization's threads and on Home when a new chat goes to one of the organization's projects. The @ button next to the attach button types the @ and opens the list.
A tagged member:
- joins the thread, which shows up in their sidebar as unread
- gets a notification on the mobile app if the message is still unread a minute later (browsers get no notification for a tag)
A member tagged again before reading the thread gets no second notification. Once they read it, the next tag notifies them again.
Memory in an organization's threads
What June learns in the organization's threads it keeps for the organization, and every member's chats there use it. It saves the shared work's facts and decisions, not personal ones, and it does not bring your personal memory or your Soul into these threads. The organization also has a Soul of its own, which June changes only when someone asks. Shared chats has the details.
Projects in an organization
A project created in the organization belongs to it: every member sees its chats, files and instructions, can start chats in it and change it, and only admins archive it (Organization projects). Where a conversation lives compares its memory, sandbox and payment with every other place.
What June does not do
- It does not answer a message that does not tag it, even one asking it a question.
- It does not use Obsidian, ownCloud or Tailscale here (the tools that act as you in the sandbox). GitHub works in the shared sandbox as whoever wrote the message June is answering, never as someone else.
- It does not set up a schedule from an organization's chat on the web.
