In some examples, the subscription user interface 400 can include an authorization user interface element, which can enable the user to provide authorization for the subscription. In at least one example, such an authorization indication can be a control or other selectable element (e.g., “Accept” in FIG. 4B), which can be associated with an actuation mechanism. Actuation of the mechanism can provide an authorization indication (e.g., an indication of authorization) to be sent from the application 140 to the server(s) 102. In at least one example, based at least in part on receiving an authorization indication from the application 140, the subscription management component 116 can generate a subscription. In some examples, a subscription can be specific to a particular user. In some examples, a subscription can be specific to a communication channel, direct message, board, and/or other resource associated with the communication platform. In at least one example, the subscription management component 116 can associate an indication of the subscription, in the datastore 122 for instance, with the object and/or application, the user associated with the subscription, the communication channel associated with the subscription, the direct message associated with the subscription, the board associated with the subscription, and/or the like. In some examples, if the subscription is associated with an object associated with the communication platform, the subscription data 124 can store the authorization indication.
