Offboarding and project closure/decommissioning

As of today all process seems oriented to add user to the system and starting a project

We face challenges at the other spectrum of a project lifecycle, the off boarding and project Closure.

Example, we need to set a date at which a user will no longer need to access the project or his access should turn in to a read only access, without having to remove him from various the groups/roles he belong. Reason is that 6 month, 1 year or 5 years later we might need to re-introduce the user to the project.


Another example a project has an end date. By contract we are request to limit the access to the archive project to a strict limited number of people. Which raise the request to have an end date for projects so the projects will become Inactive. This could be as well a manual trigger.

Also per contract we are being require to give 10 year access in read only to the client or various project participant before we can delete or clean certain project data. We would like to archive this with a simple switch for each user where we would turn access to the document they are entitle into a read only access. Again we need to preserve the original access and right incase we need to reactivate the project at a later time.

In resume onboarding is an important aspect to start a project, but the off boarding ( decommissioning) of a project is has important and we need tools and processes to achieve this.