Why do we use lifecycle states in vault? Because we want to track where in the process our design is, in line with our business process, and allow others access to those designs at the right time. Typically though our state change indicates that other functions need to happen, such as translations, notifications, and general information distribution to all required stakeholders. Often an admin overhead that impacts our time available for innovation, Vault can be customised to automatically trigger and take care of these mundane tasks for you. The only problem is you have to be a coder to put these in place and, once in place, further code change may be needed when your processes need to change. Sovelia Vault offers the best of both worlds; A configurable add in to vault that any competent administrator can adjust and use. It offers the automation to recover that design time, but without the shackles of holding you back when your processes evolve.