The QBO Security module include a standard registration feature that can be easily extended to handle custom use cases. The Person/Register method will:
This does not actually grant the registered user access to the system. To do that, either:
A client required that users specify a bank identifier upon registration, and if that bank identifier was valid, the user be automatically activated, become a member of a role, and be granted access to the Organization record associated with the bank identifier. This requirement was handled by creating a custom statement: Person/RegisterServicer. This statement used PersonID and Servicer parameters to handle the requirement.
Typical QBO multi-tenant installation base each tenant on an Organization. Several themes support registration using this construct, including QCM and QRM. A security administrator uses the User panel in Organization/Summary to register new users. The Person/RegisterProcessor statement handles this:
The Quandis Forms Hub allows companies to present any sort of form (task) to the outside world on a secure, neutral site (forms.quandis.net). In order for a user to submit a form, the user must register. Some banks wish to:
The following Person/RegisterDomain statement handles this, assuming a company has set up their Registration Whitelist and Blacklist as ContactMethod rows:
See Theme.forms > Config > Setup.HostedForms.xml for a full package to handle this use case.