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.