predetermined period of time (e.g., thirty seconds, one minute, two minutes, five minutes, one day, etc.). Upon expiration of the predetermined period of time, the notification can be dismissed so that the user is no longer being notified of the request. Furthermore, the system may enable the user requesting the attention to set the period of time for which the notification is to persist before being dismissed. For instance, a user may define that a user interface element requesting attention be displayed for five minutes. After that five minutes, the user requesting the attention wants to continue editing the content by incorporating the feedback provided by those that reviewed the content. Consequently, any feedback received after five minutes may no longer be as effective. In additional or alternative examples, the user requested to provide attention can be presented with an option to manually dismiss or ignore the notification if the user thinks a review of the content is not important. [0071] In some configurations, a request for attention can be attached to an object (e.g., a diagram or text drawn on a section of a whiteboard). Thus, if the object is deleted, the request for attention is terminated. Moreover, if the object is moved from one section of a whiteboard to another section of the whiteboard, then the request for attention moves with the object (e.g., a user interface element can be updated to indicate a location of an object to be reviewed). Even further, the request for attention can be associated with a state of an object, where the state of an object is associated with a timestamp. Accordingly, when a reviewer selects a user interface element to view content, based on a request for attention, the system can display the object in its state at the time attention is requested. In some instances, the system can also display the object in its current state so that the reviewer can compare the state of the object at a time attention is requested to a current state of the object at a time the reviewer chooses to review the object (e.g., the reviewer can compare the two states of the object to determine edits that occur between when attention is requested and when attention is provided). [0072] FIG. 8 is a flow diagram illustrating a routine 800 for enabling aspects of the present disclosure. In various examples, operations of the routine 800 can be performed by the server computer 112 and/or a client computing device. It should be appreciated that the logical operations described herein with regard to FIG. 8, and the other FIGS., can be implemented (1) as a sequence of computer implemented acts or program modules running on a computing device and/or (2) as interconnected machine logic circuits or circuit modules within a computing device. [0073] The particular implementation of the technologies disclosed herein is a matter of choice dependent on the performance and other requirements of the computing device.