LISA BusinessPro ships with three in-built roles. These are:
Subscription Admin
Users assigned this role have full CRUD access within the Enterprise subscription automation module. Subscription admins have the following major responsibilities:
- Initial deployment and maintenance of the LISA parameters and configuration entities. This might be in collaboration of administrators of other modules of the system (such as General Ledger) unless the user has the necessary rights across modules.
- Configuration of the Master subscription batch process.
- Creation and publishing of subscription plans (and lines) upon contract signature and/or subscription procurement and deployment.
Subscription Manager
Users assigned this role have full CRUD access within the Enterprise subscription automation module excluding the setup sub-menu. This is ideal in scenarios where some is responsible to manage the subscription business end-to-end but is not allowed to change the module’s core parameters
Subscription Project Manager
Users assigned this role have read only access to subscription plans. They can also publish/un-publish subscription plans and create subscription plans from the “Transfer to WBS” dialog of a project in the Project and Accounting module.
Subscription Clerk
Subscription clerks can modify, firm and post subscription actions but cannot change the module’s parameters or configuration entities. The typical day in the life of a subscription clerk (and associated training) can be greatly simplified as he/she needs only to be trained on how to use the Subscription actions list page and does not need to be given extensive training in General Ledger, Purchase Ledger or Sales Ledger. In fact, the entire “subscription contract to cash” process can be executed without even going into the Sales Order, Purchase Order or Payment Journal forms. Subscription clerks have the following responsibilities:
- Review subscription actions generated by LISA’s Master subscription batch process
- Based on the information displayed in the Subscription actions list page take the necessary actions in conjunction with account managers and the finance department. Such actions could be ensuring that deposit or security top-ups are sent to customers and posted when payment received, sales invoices posted and invoice sent to customers, purchase orders created and sent to suppliers and posted when supplier invoice is received.
Subscription Viewer
Subscription viewers have read-only access to the Enterprise subscription automation module. These users could be members of the finance or accounting department, sales people, marketers, C-Level execs etc who only need to view subscription data and statistics and not take action upon it.
ProjOps Subscription Admin
This role provides (read/write) access to the subscription creation screen which is triggered from a project in Dynamics 365 Project Operations. It also provides (read/write) access to an inquires form from the Dynamics 365 Finance and Operations side to review/adjust all subscriptions created from Dynamics 365 Project Operations projects.
ProjOps Subscription User
This role provides (read/write) access to the subscription creation screen which is triggered from a project in Dynamics 365 Project Operations. This role does not provide any level of access to the admin inquiry screen to review all subscriptions created from Dynamics 365 Project Operations projects.
ProjOps Subscription Viewer
This role provides (read-only) access to the subscription creation screen which is triggered from a project in Dynamics 365 Project Operations. This role does not provide any level of access to the admin inquiry screen to review all subscriptions created from Dynamics 365 Project Operations projects.
Note: Using Dynamics 365 Project Operations is completely optional in LISA. There is no mandatory dependency.
The screenshot below shows the applicable roles if your LISA deployment does not involve the use of Dynamics 365 Project Operations.
The screenshot below shows the additional roles to be used if your LISA deployment involves the use of Dynamics 365 Project Operations.
