What SingPass integration actually involves

"Can you add SingPass login?" is a reasonable question with an unreasonably long answer. Here is the honest version.

The straightforward part is genuinely straightforward. SingPass sits on a standard identity flow, and connecting an application to it is well-trodden ground. If all you need is for a member to sign in as a verified person, that is a contained piece of work.

The part that consumes the time is everything around it. Onboarding is paperwork with a queue attached: before you write a line of code, your organisation has to be approved to consume National Digital Identity at all. The sandbox behaves differently from production in small ways that you find at the worst moment. And Myinfo requires you to declare precisely which attributes you are collecting and why, which is a good discipline and also a form.

Then there is the question everybody underestimates: what do you do with the verification once you have it? A verified login is not the same as a verified member. Your constitution has rules about who may vote, and mapping a SingPass identity onto your membership register is the actual project.

Virtual AGMs are where this gets sharp. An AGM has to satisfy your constitution and your auditor. That means verified attendance, quorum counted only from verified attendees, votes attributable to real identities without being publicly attributed, and proxies handled correctly. Getting the login working is perhaps a fifth of that.

This is what SecureMeet exists to absorb. We have done the onboarding, the identity mapping and the quorum arithmetic often enough that it is now boring, which is the correct state for anything standing between your members and a valid vote.

If you are weighing this up, the useful question is not "how hard is SingPass". It is "what decision does this verification need to be strong enough to support". Come and ask us. The first conversation is free.