Skip to content

TopicsPage by page

A topic's page

A topic’s page is where you work something out with the agent. Your chat is on one side, and the topic’s document, which the agent writes as you talk, is on the other. Open a topic by clicking its title on the topics list, or go to its key’s address, such as /topics/ACM-281.

Open the topics list (opens Emargen in a new tab)

In the pictures, someone in customer success at ACME, the company in the docs’ pictures, has asked if a customer’s team managers can export their team’s access. In this picture, the document is folded to a small picture on the right.

The topic ACM-281: its key and title at the top with Sharing (Everyone), a filled star and a ⋯ menu; History folded to one line above Ana's question, the agent's steps and its answer; the message box at the bottom; a small picture of the document on the right.The topic ACM-281: its key and title at the top with Sharing (Everyone), a filled star and a ⋯ menu; History folded to one line above Ana's question, the agent's steps and its answer; the message box at the bottom; a small picture of the document on the right.
  1. Where you are. Topics, then the topic’s key and title. Click Topics to go back to the list.
  2. Sharing. Who can open the topic now. Click it to change that (see Sharing).
  3. The star. Stars the topic for you alone, under Starred in the menu. On a starred topic it says Unstar, and on any other Star.
  4. The ⋯ menu. Everything else you can do with the topic (see The ⋯ menu).
  5. History. What has happened to the topic, folded to one line once your chat has started. Click it to open it (see History).
  6. Your message. Copy message copies it, and Edit message lets you change what you asked.
  7. Thought for 28 seconds. Click it to read how the agent went about your message.
  8. What the agent did, a line for each thing in order, such as Named it, Set, Started the document and Checking. Click a line to open the document where it changed.
  9. The agent’s answer, with Copy message under it.
  10. Emargen. The persona that answers you (see The persona).
  11. The message box. Reply, ask for more, or tell the agent what to change.
  12. The document, folded. Click it, or its Open button, to open it beside the chat (see The document).

Your chat with the agent is your own. Everyone who can open the topic has their own chat on it. If you take part, the agent in your chat writes into the one document everyone shares.

Under the message box, Attach files adds a file for the agent to read, and Send sends your message. Expand the message box makes the box bigger, with formatting, as on New topic. Type / at the start of a message for the commands and skills you can call. “/clear” empties the chat. The agent keeps a short summary of what came before, and “Show earlier” brings the old messages back into view.

When the agent wants to change something you have to agree to, like shaping the topic as a template, it puts the change on a card with its own button and Cancel. Nothing changes until you press the button. Under its latest answer, the agent may offer one or two next steps as buttons, like a question you’d likely ask next. It offers none while a question, a card or unfinished work is pending.

When an answer can’t finish, the agent shows a line that says what happened, such as the AI service not answering. “Send again” beside it sends your message once more. What the agent did before it stopped stays on the topic. If the line says no model is set for chats, the people who manage models in your organisation can set one.

History lists what happened to the topic, read from its versions. Each line says who did what, such as who wrote it, set a field or changed a section. When there are many, the middle ones fold into one line. A topic someone else started, or an agent task made, opens on its document when you’ve never talked in it. Your empty chat shows its History in full. Under it are a few questions to start with, like What is the short version? Click one to ask it. Once you send a message, the History folds to one line above your chat.

ACM-307 as Ana sees it before she has asked anything: History in the chat, with Thu 8 Oct, Agent task Customer questions from support, Wrote it, and Tue 13 Oct, Tom Weber, Changed What we tell them; two questions to ask under it; the document open on the right, with the template Customer question and a chip From Customer questions from support above the title, the fields, and Labels with Add a label.ACM-307 as Ana sees it before she has asked anything: History in the chat, with Thu 8 Oct, Agent task Customer questions from support, Wrote it, and Tue 13 Oct, Tom Weber, Changed What we tell them; two questions to ask under it; the document open on the right, with the template Customer question and a chip From Customer questions from support above the title, the fields, and Labels with Add a label.
  1. History. Each line says when, who, and what they did.
  2. Questions to ask. Click one, and it’s sent to the agent.
  3. From Customer questions from support. The agent task that made the topic. Point at it to read what the task does. Click it to open the list it fills.
  4. Add a label. Beside Labels, on a topic with none yet.

An agent task that fills a list makes a topic for each thing it finds, and keeps it up to date. The task owner’s chat on such a topic holds what their task asked the agent, in their name, and the agent’s answer.

A persona is how the agent works for you: what it knows and how it answers. Click the persona’s name above the message box to pick another. See Personas and skills.

The persona picker: a Find a persona box; under Organisation, Emargen (starred as the default and ticked), Security reviewer and Support analyst; under Yours and shared, Implementation planner and Sales engineer.The persona picker: a Find a persona box; under Organisation, Emargen (starred as the default and ticked), Security reviewer and Support analyst; under Yours and shared, Implementation planner and Sales engineer.
  1. Emargen. A persona, with a line on what it is. The star marks your default, and the tick the one answering now.
  2. Organisation. The organisation’s personas.
  3. Yours and shared. Your own personas and those shared with you.

At the foot of the list, Manage personas opens the personas in your workspace.

Click the document’s small picture to open it beside the chat.

ACM-281 with the document open: Chat and Comments tabs above the chat on the left, Comments with a count of 1, the document on the right with its template, title, fields, labels, lists and first sections, and three small buttons at the top right.ACM-281 with the document open: Chat and Comments tabs above the chat on the left, Comments with a count of 1, the document on the right with its template, title, fields, labels, lists and first sections, and three small buttons at the top right.
  1. Chat and Comments. Switch the left side between your chat and the topic’s comments. The number counts the open ones (see Comments).
  2. The divider. Drag it to make the chat or the document wider.
  3. Hide the chat. Folds the chat away, so the document has the page. ⌘J does the same.
  4. Full width, Full screen and Minimise. Widen the document, show it on the whole screen, or fold it back to its small picture.
  5. The document, with the topic’s fields, labels and lists at the top.

The agent writes the document. You don’t type into it. To change the document, ask the agent in the chat.

The top of ACM-281's document: the template Customer question, the title, the sentence under it, the fields Customer, Status, Reply by and Product area, Labels with Add a label, Lists with This week and a button to change them, and the buttons 2 versions and Contents.The top of ACM-281's document: the template Customer question, the title, the sentence under it, the fields Customer, Status, Reply by and Product area, Labels with Add a label, Lists with This week and a button to change them, and the buttons 2 versions and Contents.
  1. Customer question. The template the topic follows. Click it to open the template.
  2. The title, and the sentence under it on what the topic is about. The agent writes both.
  3. Customer. A field from the template. Click its value to change it.
  4. Status. Another field (see Changing a field).
  5. Reply by. A date field. Click it to choose another day.
  6. Add a label. The topic has no labels yet (see Labels and lists).
  7. Change lists. The button beside the lists the topic is on.
  8. 2 versions. How many versions the topic has (see Versions and contents).
  9. Contents. The document’s sections. Click one to go to it.

Beside the versions count, a topic counts its files and its sources once it has some. A topic with no fields shows only its labels and lists.

Click a field’s value and pick another. Each field says what it’s for at the top of its list.

The Status field's list: Where our answer stands, then Open, Waiting on the customer (ticked) and Answered, and Clear.The Status field's list: Where our answer stands, then Open, Waiting on the customer (ticked) and Answered, and Clear.

Clear empties a field that holds a value, and an empty field says Empty. A date field like Reply by opens a calendar. The agent changes fields too, and you’ll see Set in the chat when it does. Only people who take part change fields. Someone who reads it sees the values.

The button beside the labels opens the organisation’s labels, each with a tick box. On a topic with labels it reads Change labels, and on one with none, Add a label.

Labels for Kelderby: single sign-on before go-live: the line Type a new name to make a label., a Find or make a label box, the organisation's labels in a list that scrolls, from Almwerk Foods down, with Kelderby ticked, and Cancel and Save.Labels for Kelderby: single sign-on before go-live: the line Type a new name to make a label., a Find or make a label box, the organisation's labels in a list that scrolls, from Almwerk Foods down, with Kelderby ticked, and Cancel and Save.
  1. Find or make a label. Type to find a label, or a new name to make one.
  2. A label, ticked when the topic has it.
  3. Save. Keeps the change. Cancel leaves without it.

Labels belong to the organisation, so everyone who sees the topic sees the change, and anyone who can open the topic can change them.

Change lists opens the lists you can put the topic on. A tick puts it on a list or takes it off, at once.

The Lists picker: a Find or name a list box; Workspace lists with Support questions and This week (ticked); Go-lives, a board, with its lists; Support, another board, with its lists; and the line Automatic lists can't be picked here.The Lists picker: a Find or name a list box; Workspace lists with Support questions and This week (ticked); Go-lives, a board, with its lists; Support, another board, with its lists; and the line Automatic lists can't be picked here.
  1. Find or name a list. Type to find a list, or a new name to make one.
  2. Workspace lists. The lists you see in your workspace.
  3. Go-lives. A board’s own lists, under the board’s name.

Lists that fill themselves aren’t picked by hand, and the picker says so. On a topic on no list, the button reads Add to a list.

2 versions opens the topic’s versions, newest first, each with who made it, what changed and when.

ACM-281's versions, newest first: v2, Tom Weber, with the topic agent, Changed What we tell them · Status Open → Waiting on the customer, Mon 12 Oct, 14:10; v1, Ana Ruiz, with the topic agent, Created the topic: wrote The question and What exists today · Customer set to Northgate · Status set to Open · Reply by set to Tue 20 Oct, Sat 10 Oct, 09:30.ACM-281's versions, newest first: v2, Tom Weber, with the topic agent, Changed What we tell them · Status Open → Waiting on the customer, Mon 12 Oct, 14:10; v1, Ana Ruiz, with the topic agent, Created the topic: wrote The question and What exists today · Customer set to Northgate · Status set to Open · Reply by set to Tue 20 Oct, Sat 10 Oct, 09:30.
  1. v2. The newest version.
  2. v1. The first version, which created the topic.

Click a version to read the topic as it was then: see A version of a topic. Contents lists the document’s sections. On a topic with tabs, it lists each tab’s sections under its name.

The Contents list of ACM-281: The question, What exists today, What we tell them.The Contents list of ACM-281: The question, What exists today, What we tell them.

The document is made of sections, each with a heading. Point at a heading to see its ⋯ button. A section nobody has written yet shows, in grey, what the template says goes there.

ACM-281's document down to its sections: What exists today, with a ⋯ button beside its heading and a box saying Exists in part, Checked 10 Oct, with what the agent found and where; then What we tell them, with a comment mark and the count 1 beside its heading, a paragraph, and an open decision: Do team managers get their own export? with a Decide button.ACM-281's document down to its sections: What exists today, with a ⋯ button beside its heading and a box saying Exists in part, Checked 10 Oct, with what the agent found and where; then What we tell them, with a comment mark and the count 1 beside its heading, a paragraph, and an open decision: Do team managers get their own export? with a Decide button.
  1. More actions for What exists today. The section’s ⋯ menu (see below).
  2. Exists in part. What the agent found when it checked a question against your organisation’s sources. It can also say Exists, Missing or Unclear.
  3. Checked 10 Oct. When it checked. Under it, what it asked and what it found.
  4. portal · access report. Where it looked.
  5. 1 open comment. Comments on this section still open (see Comments).
  6. An open decision: the question, the option the agent recommends, and the alternatives.
  7. Decide. Decides it (see Deciding an open question).

A section’s ⋯ menu:

A section's menu: Comment, Draw this, Turn into a subtopic, Keep it up to date…A section's menu: Comment, Draw this, Turn into a subtopic, Keep it up to date…
  • Comment opens the Comments tab, with your comment set to be about that section.
  • Draw this asks the agent to add the one picture that shows the section best, such as a diagram, a map or a chart. It changes nothing else in the section.
  • Turn into a subtopic moves what the section holds, with its comments, into a new subtopic under this topic, and leaves a link in its place. It happens at once, and a message names the new key. People who take part see it on a section that has something written in it.
  • Keep it up to date… sets up an agent task that keeps this section (see Setting up an agent task). On a topic that already has a task, only the task’s owner has the item. It opens the task’s form with this section picked. Saving changes the task.

A topic can have tabs, each with its own sections. The tabs sit under the versions count and stay at the top as you scroll. Everything above them, from the title to the counts, is the same on every tab. In the picture, a rollout plan with two tabs and a timeline.

ACM-319, Kelderby go-live: the rollout, depot by depot, with its document open: the tabs Rollout (picked) and Open with Kelderby under 1 version and Contents, then the section The two weekends with a timeline from 20 October to 2 November and a button to open it full screen.ACM-319, Kelderby go-live: the rollout, depot by depot, with its document open: the tabs Rollout (picked) and Open with Kelderby under 1 version and Contents, then the section The two weekends with a timeline from 20 October to 2 November and a button to open it full screen.
  1. The tabs. Click one to read its sections.
  2. “Open the diagram”. Shows the diagram on the whole screen.

The address keeps the tab you’re on, so a link opens the same tab. A link to a section opens its tab. The agent never switches tabs under you. When it writes in another tab, a dot marks that tab.

A map shows who does what, or how things connect, and you can ask about it. Above it are its pills: “Everything”, then the views the agent gave it. Picking a pill lights that part of the map. Click a shape to see what’s known about it, and what you can ask.

A map in ACM-319 of one depot's switch, in four lanes, with the pills Everything and What Kelderby still has to tell us and an open button above it. The open question Who approves each depot's switch? is picked, marked Unknown, and its popover lists two next questions, then Ask how it connects to…, Strike, Quote and Comment.A map in ACM-319 of one depot's switch, in four lanes, with the pills Everything and What Kelderby still has to tell us and an open button above it. The open question Who approves each depot's switch? is picked, marked Unknown, and its popover lists two next questions, then Ask how it connects to…, Strike, Quote and Comment.
  1. The pills: “Everything”, and a view the agent made.
  2. “Open the map”. Shows the map on the whole screen, where you can zoom and pan.
  3. A picked shape, with how sure anyone is of it and who might know more.
  4. A next question. Click it, and the agent looks in your sources and adds what it found to the map, each part marked with how it’s known.
  5. “Ask how it connects to…”. Pick another shape, and the agent checks how the two connect.
  6. “Strike”. Asks the agent if the shape still holds.
  7. “Quote” puts the shape into your chat, and “Comment” opens a comment on it.

When you ask how two shapes connect, or strike one, the agent draws the change it proposes on the map, with a card in the chat. “Keep” on the card writes it. When your sources don’t support it, the agent says why. A map that tells how something happened has a pill to replay it, event by event. You can present a map with a path. “Present” shows one step at a time on the whole screen, and others on the topic can follow along.

Decide on an open decision opens the options.

The Decide dialog: Decide: Do team managers get their own export? with two options, Yes, for their own team (recommended and picked) and No, administrators send it, a Reason box marked optional, and Set aside and Decide buttons.The Decide dialog: Decide: Do team managers get their own export? with two options, Yes, for their own team (recommended and picked) and No, administrators send it, a Reason box marked optional, and Set aside and Decide buttons.
  1. The options. Pick one. The agent’s recommendation is marked and picked to start with.
  2. Reason. A sentence on why, for the next reader. You can leave it empty.
  3. Set aside. Puts the decision away without choosing. It stays on the topic, marked Set aside.
  4. Decide. Decides it with the option you picked.

Decide is there for the owner and everyone who takes part. The decision goes into the topic’s current version, and leaves Decisions. See Decide an open question.

Your notes, at the end of the document, lists notes the agent or your coding agent left you about this topic. It also lists notes you turned into this topic. Only you see them. With none, the part doesn’t show.

Your notes at the end of ACM-281's document: Only you see these. Everyone else sees their own notes here., and one note, a todo N3, Ask Northgate when their audit is, and in what format they want the export, from 10 Oct.Your notes at the end of ACM-281's document: Only you see these. Everyone else sees their own notes here., and one note, a todo N3, Ask Northgate when their audit is, and in what format they want the export, from 10 Oct.
  1. A note: its kind, its key, its title and when it was left. Click it to open the note.

See Notes from coding agents and a note.

The Comments tab holds the topic’s comments, where people talk to each other rather than to the agent. In the picture, a colleague in sales has asked the owner about What we tell them.

The Comments tab of ACM-281: Tom Weber's comment on What we tell them, Ana, Northgate's audit is on 4 December. Can I promise them the spreadsheet by then, or should I offer only the PDF?, with Reply, Resolve and Make it a decision under it; then a comment box set to Whole topic, and a Comment button.The Comments tab of ACM-281: Tom Weber's comment on What we tell them, Ana, Northgate's audit is on 4 December. Can I promise them the spreadsheet by then, or should I offer only the PDF?, with Reply, Resolve and Make it a decision under it; then a comment box set to Whole topic, and a Comment button.
  1. Comments. The tab, with how many comments are open.
  2. What we tell them. The section the comment is about. Click it to go there.
  3. Reply. Answers in the same thread.
  4. Resolve. Closes the thread, for the topic’s owner and whoever started it. Resolved threads fold away under the open ones, and Reopen opens one again.
  5. Make it a decision. The agent drafts the comment’s choice as a decision, with its options and the one it recommends. You check the draft and open it, and it waits on the topic and in Decisions.
  6. Comment on. What your comment is about: Whole topic, or one section.
  7. The comment box. Type @ to tag someone.
  8. Comment. Posts it.

Tag someone with @, and the comment waits for them in their Inbox until they reply or the thread is resolved. Their topics list shows You on the topic meanwhile. You can delete a comment you wrote while its thread is open, and its replies go with it.

The ⋯ at the top right holds everything else you can do with the topic.

The topic's ⋯ menu: Copy link, Labels…, Lists…, Add a subtopic, Move to…, Set up an agent task…, Save as a new template, Stop using its template, Manage templates.The topic's ⋯ menu: Copy link, Labels…, Lists…, Add a subtopic, Move to…, Set up an agent task…, Save as a new template, Stop using its template, Manage templates.
  • Copy link copies the topic’s address.
  • Labels… and Lists… open the same pickers as the buttons beside the labels and the lists in the document.
  • Add a subtopic opens New topic for a topic under this one.
  • Move to… puts the topic under another topic, or back on its own. Only the owner has it.
  • Set up an agent task… sets up a task the agent runs on a schedule. Once the topic has one, it reads “Agent task:” and the task’s name.
  • Save as a new template makes a template from this topic.
  • Stop using its template takes the template off.
  • Manage templates opens the templates in your workspace.

The menu has no item for an initiative. To start one that draws on the topic, see Start an initiative from a topic.

Move to… asks where the topic goes.

Move ACM-281 to…: an Under list set to No parent, and Cancel and Move, with Move greyed.Move ACM-281 to…: an Under list set to No parent, and Cancel and Move, with Move greyed.

Pick a topic in Under, or No parent for a topic of its own, then Move. Type in Under to find a topic. If the topic can’t go under one, like one of its own subtopics, the list says why. When the move changes who sees the topic, the dialog says who will see it and who won’t any more.

Stop using its template asks first when the template’s fields hold values.

Stop following Customer question?: 3 values are removed: Customer, Status and Reply by. The topic's history still shows them. Cancel and Stop following.Stop following Customer question?: 3 values are removed: Customer, Status and Reply by. The topic's history still shows them. Cancel and Stop following.

Stop following takes the template and its fields off. The sections stay, and the versions keep the values the fields had.

Set up an agent task… opens a new agent task for this topic, so the agent does the work again on a schedule and keeps the topic up to date. See A topic the agent keeps and Have the agent keep a topic up to date.

The New agent task panel: Instructions with a Name box and an Instructions box, Agent's interpretation, Output with Each run (Updates this topic or Adds a subtopic) and Updates, and Schedule with First day and Time.The New agent task panel: Instructions with a Name box and an Instructions box, Agent's interpretation, Output with Each run (Updates this topic or Adds a subtopic) and Updates, and Schedule with First day and Time.
  • Name: how the topic’s versions name the task’s runs.
  • Instructions: in your words, as you’d ask the agent in this topic. Under Agent’s interpretation, the agent shows where it looks first, how far back it reads, and who “me” is.
  • Each run: Updates this topic or Adds a subtopic, a new topic under this one each run.
  • Updates: a Section or field, or The whole topic, its title and sentence too. A run changes these and nothing else.
  • Schedule: First day and Time, in your time zone. Repeats is Once, Every weekday, Weekly or Monthly.

Then Create, and the task opens in the panel (see A topic kept by an agent task).

Click Sharing to choose who can open the topic and what they may do. See Sharing and Share a topic.

The Sharing box for ACM-281: Only me, Shared and Everyone, with Everyone picked; Ana Ruiz, ana.ruiz@acme-hq.example, as Owner; Everyone in the organisation, who Reads; Tom Weber, who Takes part, and Quinn Maas, who Reads, each with a button to stop sharing; Add people; Cancel and Save.The Sharing box for ACM-281: Only me, Shared and Everyone, with Everyone picked; Ana Ruiz, ana.ruiz@acme-hq.example, as Owner; Everyone in the organisation, who Reads; Tom Weber, who Takes part, and Quinn Maas, who Reads, each with a button to stop sharing; Add people; Cancel and Save.
  1. Only me, Shared and Everyone. Only you, the people you add, or everyone in the organisation as well. A topic a flow guides is also read by the people the flow names.
  2. Owner. The person the topic belongs to.
  3. Access for everyone. With Everyone, what everyone in the organisation may do: Reads or Takes part.
  4. Access for Tom Weber. The same for one person.
  5. Stop sharing with Tom Weber. Takes that person off.
  6. Add people. Pick someone from the organisation. People already on the topic are greyed out.
  7. Save. Keeps your changes. Cancel leaves without them.

Everyone lets anyone in the organisation open the topic, but it shows on the topics list only of the people named here.

In the pictures, an agent task keeps a topic every Monday. A section the task keeps has a mark beside its heading.

ACM-287 with the document open: the section This week's questions with a small mark beside its heading, and a table of customers, what they asked, and the topic, under 1 version.ACM-287 with the document open: the section This week's questions with a small mark beside its heading, and a table of customers, what they asked, and the topic, under 1 version.
  1. Updated by What customers asked this week. The task keeps this section. Click the mark to see the task.
  2. 1 version. Each run that changes something adds one.
  3. The kept section.

Clicking the mark opens the task:

The agent task What customers asked this week: Next run Mon 2 Nov, 09:00; Schedule Every Monday at 09:00, Each run Updates the topic, Updates This week's questions, Owner Ana Ruiz; Instructions; Runs, with one run on Mon 19 Oct that found nothing new; and Edit, Run now, Pause and Delete buttons.The agent task What customers asked this week: Next run Mon 2 Nov, 09:00; Schedule Every Monday at 09:00, Each run Updates the topic, Updates This week's questions, Owner Ana Ruiz; Instructions; Runs, with one run on Mon 19 Oct that found nothing new; and Edit, Run now, Pause and Delete buttons.
  1. When it runs next. Under it: its Schedule, what Each run does, what it Updates, and its Owner.
  2. Instructions. The task’s instructions, in the owner’s words.
  3. Runs. Each run: when, the version it made, what it changed and the tokens it used.
  4. Edit. Changes the task.
  5. Run now. Runs it once now.
  6. Pause. Stops it running until you start it again.
  7. Delete. Deletes the task.

A subtopic sits under another topic. In the pictures, a sales engineer’s single sign-on answers sit under a customer’s security questionnaire.

The subtopic ACM-284 as Tom sees it: the path Topics, Halden Foods: security questionnaire, ACM-284 at the top, and the document Halden: single sign-on answers.The subtopic ACM-284 as Tom sees it: the path Topics, Halden Foods: security questionnaire, ACM-284 at the top, and the document Halden: single sign-on answers.
  1. Halden Foods: security questionnaire. The topic it sits under, in the path at the top.
  2. Halden: single sign-on answers. The subtopic’s own document.

Sharing on a subtopic has one more switch.

Sharing for ACM-284: the switch Same as Halden Foods: security questionnaire, switched on, above the questionnaire's sharing, greyed: Everyone, Tom Weber the owner, everyone in the organisation reads, Mira Holm takes part, Ana Ruiz and Quinn Maas read.Sharing for ACM-284: the switch Same as Halden Foods: security questionnaire, switched on, above the questionnaire's sharing, greyed: Everyone, Tom Weber the owner, everyone in the organisation reads, Mira Holm takes part, Ana Ruiz and Quinn Maas read.
  1. Same as Halden Foods: security questionnaire. Switched on, the subtopic is shared the way the topic above is, and changes when that topic’s sharing does. The choices under it are greyed. Switched off, it has its own. Only the subtopic’s owner switches it.

When a topic is shared with you to read, you see its document and have a chat of your own. Its agent answers about the topic and changes nothing. When you want something changed, it drafts a comment for you. The draft comes on a card that says who it mentions, and you can choose whom before you post it. In the picture, a sales engineer opens a colleague’s topic for the first time.

ACM-214 as Tom sees it: the document open on the right; on the left his empty chat with the topic's History, Tue 18 Aug, Ana Ruiz, Wrote it, two questions to ask, and a message box that says Ask about this topic.ACM-214 as Tom sees it: the document open on the right; on the left his empty chat with the topic's History, Tue 18 Aug, Ana Ruiz, Wrote it, two questions to ask, and a message box that says Ask about this topic.
  1. History. What happened to the topic so far.
  2. Your chat as a reader. Its message box says Ask about this topic.
  3. Sharing. Shows who sees the topic. Only its owner changes it.
  4. The ⋯ menu, with Copy link, Labels…, Lists… and Manage templates.
  5. The document. A section’s ⋯ menu has only Comment.

A reader still changes labels and lists. Labels belong to the organisation, so a label they add shows for everyone. A list of their own changes nothing for anyone else. Open decisions show without Decide, and fields can’t be changed.

The chat, the document and the comments take turns.

ACM-281 on a phone: a menu button, the title, search and ⋯ at the top; a Chat, Document, Comments switch; the chat with a card for the document; and the message box at the bottom.ACM-281 on a phone: a menu button, the title, search and ⋯ at the top; a Chat, Document, Comments switch; the chat with a card for the document; and the message box at the bottom.
  1. Open the menu.
  2. The ⋯ menu. On a phone it also holds Sharing and the star.
  3. Chat, Document and Comments. Switch between the three.
  4. Document. The card for the document in the chat. Click it to read the document.
  5. The message box.

Anyone who can open the topic sees this page. What you can do depends on how it’s shared with you:

  • The owner changes fields, decides, chooses who sees the topic, and has the whole ⋯ menu.
  • People who take part have their own chat whose agent writes for them. They change fields, decide, turn sections into subtopics and set up the topic’s agent task. Their ⋯ menu has everything but Move to…, and Sharing shows who sees the topic without letting them change it.
  • People who read see the document and comments, comment, change labels and put the topic on their own lists. Their chat’s agent answers about the topic and drafts comments for them.

See Sharing.