Continuing from the example above, another user (User C) associated with the communication channel with which the document was shared may not have Application B installed on their workspace. In at least one example, a user interface element can be presented proximate to the link to enable User C to generate a subscription to receive notifications associated with the object. Based at least in part on detecting an interaction with the user interface element, a subscription user interface can be presented via the user computing device of User C. In some examples, the subscription user interface can be presented by the communication platform. In some examples, the subscription user interface can be presented by Application B (e.g., via an API). User C can interact with the subscription user interface to authorize the subscription. Responsive to receiving an authorization indication (indicating the subscription is authorized), an authorization indicator (e.g., a token) can be shared with Application B, thereby allowing Application B to send notifications to User C and/or the communication channel. In some examples, notifications can be provided by Application B without the full application being downloaded onto the workspace of User C. That is, some features of Application B can be accessible while other features of Application B may not be accessible. Such partial provisioning of features can provide a “l(fā)ightweight” version of the application, Application B, to be accessible to User C. The lightweight version of the application can therefore provide some functionality to a user without requiring the user to download the full application. This can provide an improvement over existing techniques.