In some examples, third-party applications, associated with third-party platforms as described herein, can be integrated into the communication platform. In existing techniques, however, users can be required to fully install a third-party application (which can require administrative approval) before they are permitted to configure notifications, such as those described herein with respect to subscriptions. Techniques described herein enable an in-client experience to authorize third-party applications to enable a seamless, low-friction process for users to subscribe to application notifications or other subsets of functionality (e.g., “scopes”) associated with third-party applications. That is, techniques described herein enable a “l(fā)ightweight” version of a third-party application to be provided to a user, which can provide some functionality to a user, without requiring the user to download the full third-party application (and thus interact with multiple user interfaces to input information required for a full download and/or await a long administrative approval process). In some examples, a third-party platform (associated with the third-party application) can opt-in to providing a feature or set of features (e.g., a scope) without requiring full installation and/or administrative approval. That is, the third-party platform can opt-in to providing a lightweight version without requiring full installation and/or administrative approval. In some examples, the lightweight version of the application can enable the user to receive notifications (e.g., in association with a subscription), without requiring the full application to be downloaded. This can provide an improvement over existing techniques.