Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFW0011] Brand Registration on Web - UI Flow #12

Open
ProfilaMitchell opened this issue Aug 3, 2022 · 0 comments
Open

[RFW0011] Brand Registration on Web - UI Flow #12

ProfilaMitchell opened this issue Aug 3, 2022 · 0 comments
Labels
TOPIC: Identity Identity feature

Comments

@ProfilaMitchell
Copy link
Collaborator

ProfilaMitchell commented Aug 3, 2022

Table of Contents

Housekeeping

Make sure to clearly understand Type-A and Type-B requests, and the relavant limitations. Failling to follow the guidelines pertaining to the two acceptable types of RFWs will automatically lead to disfqualification of the RFW.

Take time to complete each section below with as much detail as is required to establish a comprehensive understanding about the underlying product specification.

ALL BELOW FIELDS ARE REQUIRED

The Problem

We do not currently have a way for brands to register on the Profila platform via web

User Story

As a brand I want to register on Profila so that I can use the platform to market to key customers.

High business severity - Brands need to be able to register on the platform to use it
High priority - Without brands on the platform, key functionality is missing

Request Type A/B

Type-A

User Registration on Web
DID implementation of registration

Owner

Mitchell Goudie

Summary

The UI and flow of the brand registration process is being developed for web.

Is This Really Necessary?

It is necessary to have a registration process in order to have brands. The UI has been designed to reduce brand friction during the process. Delivering a registration process that delivers this goal is the "best way" to onboard brands.

Motivation

The UI implementation of brand registration as per this RFW also facilitates brand registration via DID, as noted in the complementary RFW here.

Named Concepts

Data Subscription - Is when a brand subscribes to a certain set of user data based on their needs, and compensates the user for access to the data. The access is revoked at the end of the contract.

Examples, Risks & Assumptions

  1. Explain concretely what will manifest as a result of this RFW.
  • Brands will be able to register on Profila (via web)
  • Profila will be able to facilitate data subscription offers between brands and consumers to which they have sent an invitation code to the platform
  1. Explain how is it different from what is already manifesting i.e. what we already have?

There is currently no way for brands to register on Profila on web

  1. Explain what Profila users/brands will experience as a result of this RFW. How will they feel as a result of it? How will they benefit as a result of it?

Profila brands will be able to register on the platform as a result of this RFW.

  1. If applicable, provide sample messages for any new messages the system will display as a result of this RFW.

All sample messages are provided in the Conceptual Design section of this RFW.

  1. Define what is out of scope in this request.
  • User registration is out of scope of this RFW as it pertains only to brands
  • Brand Log in (existing account) and forgotten password is out of scope in this request as it is filed in a separate RFW.
  • The integration of Atala Prism in the registration process is out of scope in this request as it is filed in a separate RFW
  1. What are the data protection, privacy and security assumptions made for this request (example, should this be GDPR, HIPPA (healthcare), NIST compliant etc. - Speak to Michiel or Ipek!)

NIST identity control

  1. Explain how this user story will be supported (i.e customer support - if the user story fails technically, how will the user be supported).

If the brand cannot register successfully, ----

  1. Explain how this user story impacts revenue or billing (if applicable).

Creating a DID incurs a cost - we need to analyse who incurs the cost (Profila or the brand)

  1. State any additional risks identified as a result of this user story.

Risk for Profila in storage of the brand password and data

Success Metrics

Having 100% of brands who start the registration process finish it

Conceptual Design

The conceptual design of the registration process, including all fields necessary and elements of text for the brand, are included in the 'Registration' section of the Figma board below.

https://www.figma.com/file/jNZbevUZxZ87bp8qcrIBAP/Profila-Platform-(Brands)?node-id=0%3A1
Pass: Profila2022

Drawbacks

N/A

Alternatives

New Data

  • Brand sign in details - Associated phone number and password (for sign in)
  • Brand data - Name and Date of birth (only month and year)
  • Brand name
  • Company Size
  • Type of industry
  • Country of Registration
  • Website Domain

Business release date

The Profila registration and process is requested by the start of Q4/October 2022.

@ProfilaMitchell ProfilaMitchell added the TOPIC: Identity Identity feature label Aug 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TOPIC: Identity Identity feature
Projects
None yet
Development

No branches or pull requests

1 participant