We highly recommend you plan to switch your security to the Task-Based model. The security model will be listed as either Legacy or Task-Based security. Mekorma Area Page, Setup > System > Security Setup If you're not certain what security model you use, you’ll need to access the Mekorma Security Setup window and click on a company. Set security on the system level so logic can be applied across companies, greatly reducing setup time. Set Out-of-Office notifications and approval delegation. Reject whole payments or individual vouchers during the approval process. Approvers can use a mobile device to approve payments on the go with PowerApprovals installed. There’s no limit on the number of levels you can define.Īssign multiple approvers to a single threshold level.Īssign a single approver to multiple threshold levels.Įxtend approval workflow outside of Dynamics GP. Task-Based Security integrates with Dynamics GP security, allowing you to assign users tasks and roles in accordance with the AP work they perform.Īpproval Workflow supports more expansive and flexible configurations, including:īreak your threshold level down as finely as you want for total control. Task-Based Security: A Modern, Integrated Approach These two distinct ways of configuring security rules are now referred to as our ‘Legacy Security’ models. Many of you have been using Mekorma for years – and if you are a long-term customer, you are most likely using Checkbook or User-ID based security. Notify approvers by email or text when they need to approve payments.Īutomatically split batches so that fully approved payments are not held up by those waiting to be approved. Require that some or all your payments move through a digital approval process before they can be printed or processed.ĭesign security rules based on dollar-value ranges (a.k.a., Threshold Levels) and/or Vendor Class. Print signatures, or leave blank lines, based on different check amount thresholds.Ĭonfigure one default signature or a signature that is based on who approved the payment. By Checkbook, By User, By Task - Oh My!ĭepending on the Mekorma security model you use, you can do some, or all, of the following:Ĭonfigure signatures with encryption - electronic signatures will print on check payments. For our purposes, a security model allows you to define which users are allowed to perform what actions within configurable parameters. What is a security model?Ī security model is a way of specifying and enforcing an organization’s security rules. This article aims to explain what you need to know about recent security changes, and the best options for protecting your accounts payable process. Mekorma security options have evolved over time, as we’ve addressed a variety of customer needs. Additional security features can be enabled with our software, allowing you to enforce separation of duties and the controls necessary for secure payment processing. When users log in to GP, they will only be able to handle the tasks they have permissions for. Dynamics GP is a secure environment.Īccounts Payable teams that use Mekorma Payment Hub benefit from GP security by default. When configuring Dynamics GP, the first consideration is security. The ERP does not assume anything system administrators must assign specific roles and tasks that give users access to the right company database(s) and required functionality.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |