The system user ID of the end user that require access to the officer table and ability to raise requisitions. If a user does not have their user ID in this table, they will not be able to raise or approve requisitions.

Full name of the user ID.

Email address(s) that is tied to the Pronto user ID.

These codes are organized into a hierarchal tree structure to define the approval workflow of requisitions. An easy way to visualize this is with your own business's organizational chart.

A ‘?’ within the authorization code represents a wildcard character. As you remove the furthest right letter or number from the code, that will indicate which authorization code is next in the approval workflow.

Example:

You may have your CEO assigned an authorization code of A???????????. This assigns them as the final approver for any requisitions raised under the ‘A’ workflow tree.

Your CFO may then be assigned AF??????????. The ‘F’ will define a Finance workflow.

Your COO may then be assigned AO??????????. The ‘O’ will define an Operations workflow.

Each requisition that the CFO and COO raise or acknowledge will both flow up to the next level of A???????????.

Your branch Controller and Treasurer may both have an authorization code of AF1?????????. All requisitions raised or approved by these two users will flow up to the CFO, AF??????????.

Your branch Operations Manager may have an authorization code of AO1?????????. All requisitions raised or approved by these two users will flow up to the COO, AO??????????.

This can continue to be build out using all 12 characters if needed, down to the lowest level of the organization.

There is a special authorization code for users in the role of a procurement officer. These users use a full wildcard code, ????????????.

If you need to delegate your authority to another user, this can be done with the RAPS Delegation Maintenance function. See additional information on this function here ***insert link.

This is the first date you wish the delegated user to obtain the delegates authorization.

This is the last date you wish the delegated user to obtain the delegates authorization.

This mode will allow you to search for a specific user defined in the Officer Table.

This mode allows you to enter a new user record into the Officer Table. When entering a new record you will need the user name and to create and assign a 12 character authorization code.

The email address will automatically populate based on the email assigned to the users profile.

This mode can be used to correct an already existing record.

This mode can be used to remove an already existing record.

This mode can be used to view a data grid off all users and their officer limits. The “Reqn Limit” controls the user's approval limit specifically for requisitions. 

If you have decided to use the unbudgeted flag within RAPS then the “Unbudgeted Limit” will also be relevant for any requisitions raised over and beyond your approved budget. See additional information here ***insert link.

This mode allows you to view the audit log for the officer table.