The process of authorising a project may require sign-off from several levels of management. Once sign-off has been given from one level, it is passed onto the next level, and so on until all levels have given sign off and the project is activated.
A project is associated with an authorisation model when it is created. The same model may be used in many projects, but each project may have only one model.
The first authoriser to respond may either accept or reject the project. If they reject it, the project as a whole is rejected and authorisation can go no further.
If they accept it, then messages are sent to all the authorisers in the next highest level in the model. This repeats until all the levels in the model have been satisfied.
Project Authorisation Models are maintained here.
The link will open the Authorisation Models grid. It is a grid view which can be searched, sorted and customised as normal.
To add a new Authorisation Model click New , to edit an existing Authorisation Model click Edit . A pop up window will appear which will allow the creation or amendment of a Authorisation Model.
Complete the fields and click Save . Once the Authorisation Model header has been completed and saved a sub navigation will appear to allow additional entities to be a created.
These include:
Each User that will be able to authorise a project raised with the model must be set a lower and upper limit and a level for authorisation.
The link will open the Authorisation Models / Authorisers grid. It is a grid view which can be searched, sorted and customised as normal.
To add a new Authorisers click New , to edit an existing Authorisers click Edit . A pop up window will appear which will allow the creation or amendment of an Authoriser.
Complete the fields and click Save and Close .