that are online are currently viewing the same content and/or the same section). [0066] FIG. 6B illustrates an example user interface 604 that visually notifies a user of a section of a shared data unit that has received a high level of attention (e.g., a large number of users have recently switched to view content in a “hot” or “popular” section of a shared data unit). Again, in this example, graphical representations of users that have access to the shared data unit (e.g., a digital canvas) are dispersed around the edge of the user interface 604 in order to identify the users, their presence or lack thereof, and/or the location of the different content being edited relative to the content currently displayed. [0067] In this example, the visual appearance of one of the graphical representations (e.g., “KL”) is altered to indicate that the content and/or the section currently being worked on by “KL” has recently received, a high level of attention 606. Similar to the discussion above, an altered visual appearance can include flashing, a change in colors, a change in fill pattern, a change in size, etc. [0068] To determine whether a high level of attention has been reached in this example, the system may track the number of users that have viewed the content and/or a particular section over a time period (e.g., the most recent ten minutes, the most recent thirty minutes, the most recent day, the most recent week, etc.) and compare the number of users to a threshold number. If the number exceeds the threshold, then the content and/or the section qualifies as having received a high level of attention. In some instances, the threshold can be established based on a predetermined percentage of a total number of users that have access to the shared data unit (e.g., 10%, 20%, 30%, 40%, 50%, etc.). [0069] FIG. 7 illustrates an example user interface 700 that contains a dashboard of shared data units to which a user has access. As shown, the user interface 700 can separate shared data units for which attention is requested from a user from other shared data units. That is, a first section 702 may prioritize shared data units for which a user (e.g., “AB”) is being requested to review content, and a second section 704 may contain data units with content for which the user (e.g., “AB”) is not being requested to review content. As shown via the graphical elements on the data units, user “DS” is requesting that user “ AB”review content in “DataXYZ”, user “GR” is requesting that user “AB” review content in “DataABC”, and users “CB” and “LW” are requesting that user “AB” review content in “Datal23”. Accordingly, the dashboard can provide a quick snapshot of how many people are requesting the attention of “AB”, as well as a number of data units that need attention. [0070] In various examples, the notification (e.g., the user interface element) indicating that a user’sattention has been requested is configured to persist on a display screen for a