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.
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
Â
User signup flows
Root admin
Invited by FS central:
Details of the org and user already entered by FS central
Root admin receives the mail with a link to activate account and the link expires in some days
Activate account:
Username - suggested
Set up password - hints and requirement
Option to add mobile number (if not entered by FS central invitation) and enable 2FA
Add details of a reference person from the organization for emergency
Upload image of ID
Accept terms and conditions
Verification link sent to mail id
Click link
If mobile based 2FA selected then send OTP
Success
Onboarding:
Personalize themes (upload logo etc)
Guided journey to add team members resulting in adding one user
Skippable: Guided journey on features resulting in dummy connector on dummy dataset on some server
Through FS website:
Details of the org
Name
Domain
Country
Details of the user
Name
Email id
Phone number
Select plan
Basic
Certified
For certified users: User receives the mail with a link to activate account and the link expires in some days
Activate account:
Username - suggested
Set up password - hints and requirement
Option to add mobile number for 2FA
Add details of a reference person from the organization for emergency
Upload image of ID
Accept terms and conditions
Verification link sent to mail id
Click link
If mobile based 2FA selected then send OTP
Onboarding:
Personalize themes (upload logo etc)
Guided journey to add team members resulting in adding one user
Guided journey on features resulting in dummy connector on dummy dataset on some server
Team Admin/ General
Invited by the root admin:
User receives the mail with a link to activate account and the link expires in some days
Reminder mail before the link expiry
Activate account:
Username - suggested
Set up password - hints and requirement
If 2FA enabled by root admin
Enter phone number
Â
Success
Onboarding:
For Team admin only: a guided tour to add team members
For adding general users, option to enable single sign on using gmail
Option of enabling 2FA for the users
Skippable: Guided journey on features resulting in dummy connector on dummy dataset on some server
Â
Onboarding Decisions
Â
Step 1:
Should we directly jump into connector creation? Or should we give a product tour?
Give a product tour that has skippable steps. Product tour means the steps telling you about the features of the product.
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.
In the 3 steps, should we guide them through each field? Or have 1 general tooltip?
When we are activating users, yes. Not on the product tour.
Create a dummy project
That is part of the test network. There is a dummy project with dummy data set on some remote server.