You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases, we might need to make sure we know exactly who the user is to manage his access to the features. For example, we might require a proof of authorization by person submitting a grant proposal in the name of an organisation.
In these cases, the user should upload proof of authorization or we should use some governmental service to check for authorization.
Feature: KYC
As a program manager
I want to make sure only authorized persons can apply on the behalf of an organisation
Because I want to prevent impersonation
Scenario: User applies on behalf of organisation
The text was updated successfully, but these errors were encountered:
This looks like a post-MVP issue, or a lower priority one.
I think it would be ok if we just have a mechanism for whitelisting these people for now, using eg. wallet address.
Check authorization
In some cases, we might need to make sure we know exactly who the user is to manage his access to the features. For example, we might require a proof of authorization by person submitting a grant proposal in the name of an organisation.
In these cases, the user should upload proof of authorization or we should use some governmental service to check for authorization.
The text was updated successfully, but these errors were encountered: