User Status
Hi
Morgan
While amending wireframes and user stories for group and user management, we came across a situation that seems to warrant an additional user status for expired trial accounts. We feel it would be wise to not have them set to Non-Active, in order to not mix them up with non-active subscriber accounts that either expired or were manually set to that state.
We would therefore introduce a Expired (Trial) status. It wouldn't be possible to manually assign it; it would only be set once a free trial comes to an end. Admins would then have the possibility to:
Morgan
While amending wireframes and user stories for group and user management, we came across a situation that seems to warrant an additional user status for expired trial accounts. We feel it would be wise to not have them set to Non-Active, in order to not mix them up with non-active subscriber accounts that either expired or were manually set to that state.
We would therefore introduce a Expired (Trial) status. It wouldn't be possible to manually assign it; it would only be set once a free trial comes to an end. Admins would then have the possibility to:
- Extend the trial period;
- Upgrade to a subscriber account (this would trigger the Add New User flow, with a few values passed on, like name, email address and login credentials)
- Archive the account.
You can see below/attached an example of what would be the Edit Trial User page (with expiry date reached) as well as the account creation flows that led us to that conclusion.
We can discuss this further on Thursday's call if you wish.
We can discuss this further on Thursday's call if you wish.
This is a good idea, but I think we should talk it through a little on Thursday. In particular, I think the admin user should have the option to keep the expired account in the Current User table by setting the status to "Non-Active" rather than "Archived". The reason for this is that we want to be able to cross reference trial requests with past trial requests, which will determine what action is taken. For example, we will not activate requests that appear to be coming from the same person under different email addresses.
Morgan