As described above, in at least one example, the subscription user interface element can be associated with an actuation mechanism. In at least one example, based at least in part on detecting an actuation of the actuation mechanism, the application 140 can send an indication of such to the server(s) 102. The subscription management component 116 can receive an indication of such an actuation and can cause a summary user interface to be presented via the user interface 200. In some examples, the summary user interface 404 can be presented as a pop-up (as shown), an overlay, a new section of the user interface, a new user interface, etc. In some examples, the summary user interface can present a summary of notifications associated with the subscription to which the actuated actuation mechanism/user interface element corresponds. In some examples, the summary of notifications can include all notifications since a previous summary was requested, all unread notifications, all notifications associated with the subscription, a subset of notifications associated with the subscription, etc. In some examples, the notifications can be organized based on date, time, topic, priority, last interaction, etc. An example of such a summary user interface is illustrated and described above with reference to