<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=805153362943600&amp;ev=PageView&amp;noscript=1">

Secure Manager 2.1.0: Account Re-enrollment Permissions and Monetary Limits

[fa icon="calendar"] Aug 7, 2019 3:58:32 PM

We are happy to announce the release of Secure Manager 2.1.0. The new release allows our partners to manage account re-enrollment permissions and introduces new monetary limits for the unpaid invoices.

Secure Manager 2.1.0

Easily manage account re-enrollment permissions

Previously accessible only through our Secure Administration System (SAS), the account re-enrollment permissions are now also available to our partners from Secure Manager. 

The new security feature contains three management actions, that either allow, disable or restrict an operator's ability to re-enroll their device. This will provide our partners with the needed flexibility and more centralized control over their user base.

Monetary limits for Distributors and Resellers

Two monetary limits are introduced in the latest version of Secure Manager. The first limit verifies if the partner has any unpaid invoices that are overdue. If this is the case, the system will restrict the user from renewing the licenses, as well as from purchasing the new ones.

If the partner has no overdue invoices, the system will verify if they have reached the allowed credit limit for their account. The credit limit applies to all the unpaid invoices that are not overdue. The system will notify the user accordingly when they are approaching their credit limit and restrict them from purchasing new licenses or renewing the existing ones when they reach or exceed it.

Backend performance optimization

We are constantly assessing the front-end and server-side structure of Secure Manager to ensure that its content is delivered as optimally as possible to our users, offering a fast and seamless platform experience. Code optimization is commonly used to improve the front-end and server-side speed.

Code optimization involves analyzing the code and database queries and finding the spots where the code is inefficient and where database queries are slow. After finding these “hotspots,” it is a job of our developers to fix those problems. This often involves finding a better algorithm or modifying the code to work around a bottleneck (for example, hard disk space or bandwidth). For databases, this usually involves adding indexes to speed up the query, rewriting the query or modifying the structure of the database.

 

Since we are constantly striving to improve and innovate, we depend on your feedback to help shape how our products and services evolve. Please follow the link below to share your thoughts and ask any questions you might have.

 

 

Report problems, ask questions or give ideas. SUBMIT YOUR FEEDBACK

[fa icon="twitter-square"]

Topics: News, Releases, Secure Manager

Andrey Litvinov

Written by
Andrey Litvinov