A beneficiary may leave a nonprofit’s platform because they could not get past the identity verification step, even though their application is complete and they still need the service. At the same time, an impersonator may successfully access a legitimate account and change its details. Both situations place the same responsibility on the organization: to protect the service from improper use and give account holders a safe, clear way to access it.
This responsibility begins with the way digital identity is designed: how the platform recognizes users and verifies their access. Its effects extend to beneficiary data, volunteer accounts, staff workflows, and the information the organization exchanges with its service providers. For this reason, every verification measure should be assessed from two connected perspectives: the protection it provides and the burden it places on the person who needs the service.
Digital identity serves three complementary functions. Distinguishing between them helps an organization identify its needs and discuss the technical solutions presented to it.
The first function is identity proofing: when a service requires confirmation that a person is who they claim to be. This includes examining the evidence they provide and verifying its authenticity and connection to them. The level of verification required depends on the nature of the service and the consequences of misidentifying the person.
After an account has been created, authentication verifies that the person attempting to sign in controls the verification method associated with the account. This may rely on a password or another method, or combine multiple factors depending on the required level of protection. In other words, establishing a person’s identity at registration and protecting their subsequent access are important tasks, each requiring separate attention.
Federated identity comes into play when a platform relies on an external identity provider to send it an authentication result and relevant identity information. In this case, the organization needs to understand the reliability of the verification, how information is transferred, and what data it receives in order to assess the protection this connection provides.
In support services, a beneficiary’s eligibility remains separate from identity proofing. Confirming that an applicant is the right person does not automatically mean they meet the program’s requirements; eligibility must be determined using criteria and procedures appropriate to the type of assistance.
Choosing a level of protection starts with a practical question: What could happen if we misidentify this user or allow someone else to access their account? The result could be the disclosure of personal information, changes to sensitive details, or a benefit being transferred to someone other than its intended recipient. The assessment should consider harm to the individual as well as the impact on the organization and its partners.
Viewing general educational content is different from changing the details of an assistance payment. The latter could allow a benefit to be redirected, so it calls for safeguards proportionate to that impact. Requiring visitors to general content to complete complex verification, by contrast, may block access without any need related to the service itself.
This distinction helps the organization review what it asks of its users.
Some services can be provided without establishing a person’s real-world identity when this is not necessary and the risks are acceptable. Before adding a new field or requesting another document, it is worth determining what need the request serves and what could not be accomplished without it.
The more sensitive the information and operations available within an account, the greater the need for appropriate protection at sign-in. A risk assessment may call for multi-factor authentication and phishing-resistant methods. The chosen method should match the nature of the risks, be usable by the user, and be supported by secure procedures for when it is lost or stops working.
Some identity-proofing processes require sensitive information, and the responsibility to protect it begins the moment it is requested. This includes specifying the purpose for collecting it, how it will be used, who can access it, how long it will be retained, and how it will be destroyed once it is no longer needed, in accordance with applicable requirements.
Repeatedly collecting documents deserves particular scrutiny. Requesting the same document in multiple systems may increase the number of copies in circulation and the number of parties handling them without adding necessary verification. Reviewing how information moves through the organization, on the other hand, can show where it is collected, why it is copied, and what can be eliminated.
This review is especially important for nonprofits that handle sensitive family, health, or social circumstances. Information a beneficiary provides to confirm their identity or complete an application is shared within a relationship of trust. They have a right to a clear explanation of why the information is requested and how it will be handled, and procedures should be proportionate to their purpose.
A genuine user may encounter difficulties because of a weak internet connection, limited digital skills, difficulty using their device, or loss of their sign-in method. These possibilities should shape the service’s design from the outset, especially when an organization serves people with different abilities and circumstances.
Options may include human assistance, an appropriate in-person process, or an alternative verification method that provides the required level of protection. These options need clear procedures that staff know how to follow and beneficiaries can understand. Leaving difficult cases to individual discretion may prolong the wait for those affected and create opportunities to exploit exceptions.
The same care applies to account recovery. Someone who has lost their phone or can no longer use their verification method needs a clear path to regain access, while the organization needs to verify their request. It is useful to test this experience before launching the service, including how long it takes, what information is required, and how users can find out the status of their request.
Identity systems may use artificial intelligence to match biometric features, examine evidence, or detect fraud. Relying on these systems calls for a clear understanding of what they do and the limits of their results. An assessment should establish where they are used, what data they process, how they are tested and updated, and what risks their decisions may create.
When evaluating a technical proposal, an organization can ask specific questions about test results, privacy risks, and how incorrect results are reviewed. This is especially important if a verification failure could delay a beneficiary’s access to a program they need. It should also be clear who receives appeals, how they are reviewed, and what process is available to correct an error.
Once the service is running, users’ experiences can reveal issues that may not have been apparent during the design phase. Useful indicators include the verification completion rate, the number of people who abandon the process before completing it, the time needed to finish it, reasons for failed sign-ins, account recovery attempts, fraud reports, support requests, and the time taken to resolve them.
Reading these indicators together gives the organization a more accurate picture of performance. An increase in registered accounts alone does not show whether their owners can use them, and a low number of reports may conceal beneficiaries who left without asking for help. Opportunities to improve become apparent when a problem recurs at a particular step or among a particular group of users; its causes can then be examined and an appropriate solution tested.
A review can begin with one service that has a clear impact, tracking the user journey from registration through account recovery. At each step, the organization identifies the risks, necessary data, safeguards, and available assistance. It can then test the journey with people representative of its audience, document the reasons behind its decisions, and review the results with the technology team, beneficiary services staff, and program leads.
At the end of this journey, beneficiaries need to accomplish what they came to do while feeling confident that their accounts and data are safe. When an organization provides verification suited to the sensitivity of the service, explains each step, and quickly addresses difficulties, digital identity becomes part of the quality of care it provides. This commitment can be seen in a benefit reaching its intended recipient, information remaining protected, and beneficiaries being able to use the service with confidence.
Reference: NIST SP 800-63-4 Digital Identity Guidelines, U.S. National Institute of Standards and Technology, July 2025.
Comments (6)
No comments yet. Be the first to comment!