There should be a cleaning of the User database that removes any inactive users. The setting for timeperiod to be declared ‘inactive’ should be set in the config. Thinking 2 months of no activity, they get an email, 3 months, removed. Inactivity would cover everything, so if they are still using mail, that would be considered active, or just using git.
There should be a cleaning of the User database that removes any inactive users. The setting for timeperiod to be declared 'inactive' should be set in the config. Thinking 2 months of no activity, they get an email, 3 months, removed. Inactivity would cover everything, so if they are still using mail, that would be considered active, or just using git.
Implemented this in the Server Maintenance program that will be ran on a daily schedule. Currently set inactive days to 365, and the user must not have any data on their account.
Didn’t implement warning emails, as since they are inactive, they wouldn’t see the emails.
Implemented this in the Server Maintenance program that will be ran on a daily schedule. Currently set inactive days to 365, and the user must not have any data on their account.
Didn't implement warning emails, as since they are inactive, they wouldn't see the emails.
There should be a cleaning of the User database that removes any inactive users. The setting for timeperiod to be declared ‘inactive’ should be set in the config. Thinking 2 months of no activity, they get an email, 3 months, removed. Inactivity would cover everything, so if they are still using mail, that would be considered active, or just using git.
Implemented this in the Server Maintenance program that will be ran on a daily schedule. Currently set inactive days to 365, and the user must not have any data on their account.
Didn’t implement warning emails, as since they are inactive, they wouldn’t see the emails.