The limit of a maximum of 10 applications, each with only 5 allowed operations appears quite restrictive, don’t you think? Additionally, can I integrate to a backend system via API, or is it limited to WordPress support only?
A: Hi, thanks for your question! Let me address your points one by one:
Higher Tiers: The current tiers are designed to offer a strong foundation for a wide range of use cases. If your needs go beyond these limits (10 applications, 5 operations per application, and 200 users), we’d be happy to explore custom options or larger plans tailored to your requirements. Feel free to reach out—we’d love to help you find the best fit!
Integration with Backend Systems: Yes, you can absolutely integrate Latch into a backend system via API. Latch provides robust APIs that allow you to implement its functionality beyond WordPress or any specific platform. This means you can fully leverage Latch to secure your operations and build custom workflows for your application or system.
Apologies if the answer is hidden somewhere, I just can't find clear definitions of the terms used in the offer description. The use cases sound highly interesting, but it is unnecessarily difficult to understand the terms of the offer.
The AppSumo offers are equivalent to the Professional Plans on the homepage?
What is an "application" in TU Latch terms? Is that similar to a single plugin in WP? Or is that like per WP domain?
Where does the "maximum operations per application" relate to? Maybe that becomes clear when the term is clear.
How is a "user" defined? It is certainly not website users, but like admins, editors, or such system maintenance roles?
Thank you for your interest in TU Latch and for pointing out the need for clarification! Let me break this down:
-> Are the AppSumo offers equivalent to the Professional Plans on the homepage? Yes, the AppSumo offers correspond to the features and functionalities of our Professional Plans as outlined on our homepage. However, there are variations in the number of users, applications, and operations included in the offer. The core features and capabilities remain the same as those in the referenced plan.
->What is an "application" in TU Latch terms? In TU Latch terms, an "application" refers to a single system, platform, or service that is integrated and protected using our platform. For example: CMS like WordPress; In an intranet setup, an application could be the platform used for internal communications and file sharing; etc. Each application is essentially a distinct system or environment where TU Latch is applied to manage security and authorization.
-> Where does the "maximum operations per application" relate to? The "maximum operations per application" refers to the number of distinct authorizations operatons that can be configured within a single application. For example, in WordPress, operations might include managing user roles, editing content, publishing drafts, or restricting plugin access. For an intranet, this could involve user authentication via an IDP (Identity Provider), controlling document access, or managing approval workflows. In databases, it might cover query permissions, table access restrictions, or user role management.
->How is a "user" defined? "Users" are the end-users who interact with your services. They are given the ability to enable or disable various authorization operations through the Latch app (included in the plan).
Let me know if you have any other questions! I hope this clears things up! Please let me know if you have any other questions—we’re happy to help!
The 5 operations per application limit is designed to secure key actions within your application, such as user logins, sensitive data access oradministrative changes (examples). For many use cases, this covers the most critical operations that require an extra layer of security.
It feels limiting - but when these 5 are applied to the essential functions, it should work in most cases. For instance, if the actual login is set, other functionalities are not accessible anyway. So, in some cases even a single restriction/ limitation is already a good security measure.
Q: One time password through email?
Hi there, We'd like to provide users with a one time password through email. Would that be possible with TU Latch? Or with sms? Or can this only be done through your application?
A: Thanks for reaching out! Regarding your query, TU Latch does indeed support one-time passwords (OTP) as part of its authorization features. However, these OTPs are designed to be securely managed and displayed exclusively through the TU Latch mobile application as part of its advanced authorization controls.
At the moment, OTPs can only be displayed through the TU Latch mobile app as part of the authorization operation where this feature is enabled. This ensures that OTPs remain secure and fully integrated within the app's authorization control system.
If you have any further questions or need assistance exploring how TU Latch can support your use case, feel free to let us know!
Q: Can this be Integrated to a SASS authentication process?
Hi,
This looks like a great solution, I just want to be sure I have a clear understanding of its purpose and function. As an example, if we have a SASS, can this be used as a part of the authentication process by sourcing the TOTP via Latch in the authentication workflow? If that is the case, are the "user" limits noted in the listing overall for everyone who would receive an OTP, or are these limits for people would would access the administration of the Latch dashboard itself?
I see the value here, though the user limits would obviously impact the opportunity to use this in a SASS user authentication workflow.
A: Thank you for your question and interest in Latch!
To ensure I address your needs accurately, could you provide a bit more detail about what you're referring to by "SASS"? For example, are you speaking about SaaS platforms in general, or a specific system or application related to your authentication processes? This will help me provide you with the most relevant information.
Latch allows you to create an authorization process following the authentication process. For instance, after a user logs in through your existing authentication system (e.g.,IDP), you can configure Latch to add additional layers of authorization..
Regarding the user limits:
The limits noted in the listing refer to the total number of users who pair with Latch to perform operations within your application, such as authorizations after authentication or specific workflows requiring additional approvals.
These limits do not apply to individuals accessing the Latch administration dashboard for configuration or management purposes.
A: Hello, we have several schools and universities using Latch to enhance their security processes. They commonly integrate Latch with their existing Identity Providers (IDPs) to add authorization processes and an extra layer of security.
Examples include:
For students: Preventing identity theft risks during exam or document submissions. For staff: Securing operations for teachers and administrative personnel.
Additionally, the Latch plugin for Moodle allows seamless integration of Latch into the Moodle authentication process, making it simple to add this extra layer of security.
You can find more granular information about the Moodle plugin here: https://github.com/Telefonica/latch-plugin-moodle.
Q: Higher Tiers?
The limit of a maximum of 10 applications, each with only 5 allowed operations appears quite restrictive, don’t you think? Additionally, can I integrate to a backend system via API, or is it limited to WordPress support only?
Patxi_ba
Jan 29, 2025A: Hi, thanks for your question! Let me address your points one by one:
Higher Tiers:
The current tiers are designed to offer a strong foundation for a wide range of use cases. If your needs go beyond these limits (10 applications, 5 operations per application, and 200 users), we’d be happy to explore custom options or larger plans tailored to your requirements. Feel free to reach out—we’d love to help you find the best fit!
Integration with Backend Systems:
Yes, you can absolutely integrate Latch into a backend system via API. Latch provides robust APIs that allow you to implement its functionality beyond WordPress or any specific platform. This means you can fully leverage Latch to secure your operations and build custom workflows for your application or system.
Share TU Latch
Q: Clarification Deal Terms Possible, please?
Apologies if the answer is hidden somewhere, I just can't find clear definitions of the terms used in the offer description.
The use cases sound highly interesting, but it is unnecessarily difficult to understand the terms of the offer.
The AppSumo offers are equivalent to the Professional Plans on the homepage?
What is an "application" in TU Latch terms? Is that similar to a single plugin in WP? Or is that like per WP domain?
Where does the "maximum operations per application" relate to? Maybe that becomes clear when the term is clear.
How is a "user" defined? It is certainly not website users, but like admins, editors, or such system maintenance roles?
Thanks.
Patxi_ba
Jan 27, 2025A: Hi there,
Thank you for your interest in TU Latch and for pointing out the need for clarification! Let me break this down:
-> Are the AppSumo offers equivalent to the Professional Plans on the homepage?
Yes, the AppSumo offers correspond to the features and functionalities of our Professional Plans as outlined on our homepage. However, there are variations in the number of users, applications, and operations included in the offer. The core features and capabilities remain the same as those in the referenced plan.
->What is an "application" in TU Latch terms?
In TU Latch terms, an "application" refers to a single system, platform, or service that is integrated and protected using our platform. For example: CMS like WordPress; In an intranet setup, an application could be the platform used for internal communications and file sharing; etc.
Each application is essentially a distinct system or environment where TU Latch is applied to manage security and authorization.
-> Where does the "maximum operations per application" relate to?
The "maximum operations per application" refers to the number of distinct authorizations operatons that can be configured within a single application. For example, in WordPress, operations might include managing user roles, editing content, publishing drafts, or restricting plugin access. For an intranet, this could involve user authentication via an IDP (Identity Provider), controlling document access, or managing approval workflows. In databases, it might cover query permissions, table access restrictions, or user role management.
->How is a "user" defined?
"Users" are the end-users who interact with your services. They are given the ability to enable or disable various authorization operations through the Latch app (included in the plan).
Let me know if you have any other questions!
I hope this clears things up! Please let me know if you have any other questions—we’re happy to help!
Share TU Latch
Verified purchaser
Thanks, that helped a lot to be clear, Patxi-ba.
Is the limit of 5 operations per application too restrictive?
The 5 operations per application limit is designed to secure key actions within your application, such as user logins, sensitive data access oradministrative changes (examples). For many use cases, this covers the most critical operations that require an extra layer of security.
Verified purchaser
It feels limiting - but when these 5 are applied to the essential functions, it should work in most cases. For instance, if the actual login is set, other functionalities are not accessible anyway. So, in some cases even a single restriction/ limitation is already a good security measure.
Q: One time password through email?
Hi there, We'd like to provide users with a one time password through email. Would that be possible with TU Latch? Or with sms? Or can this only be done through your application?
Thanks in advance!
Patxi_ba
Jan 27, 2025A: Thanks for reaching out! Regarding your query, TU Latch does indeed support one-time passwords (OTP) as part of its authorization features. However, these OTPs are designed to be securely managed and displayed exclusively through the TU Latch mobile application as part of its advanced authorization controls.
At the moment, OTPs can only be displayed through the TU Latch mobile app as part of the authorization operation where this feature is enabled. This ensures that OTPs remain secure and fully integrated within the app's authorization control system.
If you have any further questions or need assistance exploring how TU Latch can support your use case, feel free to let us know!
Share TU Latch
Q: Can this be Integrated to a SASS authentication process?
Hi,
This looks like a great solution, I just want to be sure I have a clear understanding of its purpose and function. As an example, if we have a SASS, can this be used as a part of the authentication process by sourcing the TOTP via Latch in the authentication workflow? If that is the case, are the "user" limits noted in the listing overall for everyone who would receive an OTP, or are these limits for people would would access the administration of the Latch dashboard itself?
I see the value here, though the user limits would obviously impact the opportunity to use this in a SASS user authentication workflow.
Thanks in Advance.
Patxi_ba
Jan 22, 2025A: Thank you for your question and interest in Latch!
To ensure I address your needs accurately, could you provide a bit more detail about what you're referring to by "SASS"? For example, are you speaking about SaaS platforms in general, or a specific system or application related to your authentication processes? This will help me provide you with the most relevant information.
Latch allows you to create an authorization process following the authentication process. For instance, after a user logs in through your existing authentication system (e.g.,IDP), you can configure Latch to add additional layers of authorization..
Regarding the user limits:
The limits noted in the listing refer to the total number of users who pair with Latch to perform operations within your application, such as authorizations after authentication or specific workflows requiring additional approvals.
These limits do not apply to individuals accessing the Latch administration dashboard for configuration or management purposes.
Share TU Latch
Q: Examples of this solution
Hello,
Do you have any actual examples of applications or sites utilizing this solution for any education institutions?
Patxi_ba
Jan 21, 2025A: Hello, we have several schools and universities using Latch to enhance their security processes. They commonly integrate Latch with their existing Identity Providers (IDPs) to add authorization processes and an extra layer of security.
Examples include:
For students: Preventing identity theft risks during exam or document submissions.
For staff: Securing operations for teachers and administrative personnel.
Additionally, the Latch plugin for Moodle allows seamless integration of Latch into the Moodle authentication process, making it simple to add this extra layer of security.
You can find more granular information about the Moodle plugin here: https://github.com/Telefonica/latch-plugin-moodle.
Share TU Latch
Thanks for your reply. Does Latch integrate with MS Azure or Google IDPs?