UX problem when trying to delete a subscription as an app_user

[silently]

In the current business rules, an app_user can not delete a subscription an app_admin created (only the admin can).

This kind of works (the sub is not deleted) but there is a UX/client-side bug since the user can put the subscription to the trash, and only after having refreshed the full page will he notice that is has no effect (which is the correct behavior).

So putting the icon to the trash should fail and the user be notified "contact the administrator of THIS ORG"

[tbroyer]

Subscriptions have a subscription_type field that can be used for that (it's how it's done on the Kernel side): the value is either PERSONAL or ORGANIZATION.

Now there can be one issue: should an admin be allowed to delete a subscription from his dashboard (by dragging it to the trash bin) if it was created through my-apps (either by himself or another admin), and thus is of type ORGANIZATION?

[silently]

@OzBruno this last question for you

[OzBruno]

The normal behaviour should be : the user can't delete a subscription from his dashboard, an admin can. The admin should have the ability (in My Apps) to publish again the subscription on his dashboard.

[tbroyer]

@OzBruno you don't answer the question. The question is about a user that is also an admin and whether he can delete the subscription from his dashboard in this case or must go through my-apps (in other words: should the dashboard know that he's an admin and let him delete the subscription unlike other users? or should it treat it like any other user and the subscription can only be deleted from m-apps).

[mdutoo]

@silently's answer : ideally yes, the admin should be able to.
(NB. According to @tbroyer, this issue happens because Kernel 409 Forbidden is eaten up by Portal)