FS participant user management

Purpose

The document is for giving overview of user roles and associated flow for user signup for FS participants.

 

User roles and requirements

 

User type

Role

Requirement

Root admin

- single point of contact with FS central

- add other users

- configure login/signup for other users

- optional (all of the below)

- can see all the admins and all the teams

- mandatory

- understand terms and conditions

- security: high by default

 

Team Admin

- manage members going to use FS

- can only see his/her team members

- can’t see other teams

- can’t add admins

- optional

- understand how FS is operated

- security: similar to root admin

General

- manage projects

- manage connectors

- manage datasets interfacing

- manage repo verification

- can’t add team members

- mandatory

- understand how FS is operated

- security: medium

 

Note that the admin should be able to internally add tags for respective users he/she is adding.

 

 

  1.  

    1.  

    2.  

    3.  

    4.  

    5.  

    6.  

  2.  

    1.  

    2.  

    3.  

    4.  

    5.  

 

User signup flows

  1. Root admin

    1. Invited by FS central:

      1. Details of the org and user already entered by FS central

      2. Root admin receives the mail with a link to activate account and the link expires in some days

      3. Activate account:

        1. Username - suggested

        2. Set up password - hints and requirement

        3. Option to add mobile number (if not entered by FS central invitation) and enable 2FA

        4. Add details of a reference person from the organization for emergency

        5. Upload image of ID

        6. Accept terms and conditions

        7. Verification link sent to mail id

        8. Click link

        9. If mobile based 2FA selected then send OTP

Success

  1. Onboarding:

    1. Personalize themes (upload logo etc)

    2. Guided journey to add team members resulting in adding one user

    3. Skippable: Guided journey on features resulting in dummy connector on dummy dataset on some server

  1. Through FS website:

    1. Details of the org

      1. Name

      2. Domain

      3. Country

    2. Details of the user

      1. Name

      2. Email id

      3. Phone number

    3. Select plan

      1. Basic

      2. Certified

    4. For certified users: User receives the mail with a link to activate account and the link expires in some days

    5. Activate account:

      1. Username - suggested

      2. Set up password - hints and requirement

      3. Option to add mobile number for 2FA

      4. Add details of a reference person from the organization for emergency

      5. Upload image of ID

      6. Accept terms and conditions

      7. Verification link sent to mail id

      8. Click link

      9. If mobile based 2FA selected then send OTP

    6. Onboarding:

      1. Personalize themes (upload logo etc)

      2. Guided journey to add team members resulting in adding one user

      3. Guided journey on features resulting in dummy connector on dummy dataset on some server

  1. Team Admin/ General

    1. Invited by the root admin:

      1. User receives the mail with a link to activate account and the link expires in some days

      2. Reminder mail before the link expiry

      3. Activate account:

        1. Username - suggested

        2. Set up password - hints and requirement

        3. If 2FA enabled by root admin

          1. Enter phone number

        4.  

Success

  1. Onboarding:

    1. For Team admin only: a guided tour to add team members

      1. For adding general users, option to enable single sign on using gmail

      2. Option of enabling 2FA for the users

    2. Skippable: Guided journey on features resulting in dummy connector on dummy dataset on some server

 

Onboarding Decisions

 

Step 1:

  1. Should we directly jump into connector creation? Or should we give a product tour?

    1. Give a product tour that has skippable steps. Product tour means the steps telling you about the features of the product.

    2. Give a user activation tour which has a test network with test data. Here, the user should be guided in configuring a connector and deploying it with usage controls. Should have messages that make user(s) feel good - Congratulations! Got your first connector working on the test network.

  2. In the 3 steps, should we guide them through each field? Or have 1 general tooltip?

    1. When we are activating users, yes. Not on the product tour.

  3. Create a dummy project

    1. That is part of the test network. There is a dummy project with dummy data set on some remote server.