Onboarding Product & Tech Scoping

[MohitNSamagra]

Problem

It is hypothesised that the current onboarding experience is causing a dropoff as users see multiple channels on discord that they can go to, causing them to not authenticate their GitHub.

Current Status

For this the current system understanding is required which has not been a part of handover till now.

Goal
To simplify the current onboarding flow by introducing dyno bot. The current flow opens 8 channels on discord but the goal is to allow access to limited channels and only after certain conditions are met.

Acceptance criteria

• User joins the server and has access to only 1 channel(called authorize)
• User authorizes GitHub successfully which allows them access to 'Role' channel which includes role assignment
• User answers questions in the 'Role' channel which assigns them roles
• User is then given access to all the other channels on the server

[MohitNSamagra]

• @MohitNSamagra to pick on 27th

[MohitNSamagra]

• @MohitNSamagra to pick on 2nd Jul

[MohitNSamagra]

• Clarity received on analytics
• Testing to be done by @MohitNSamagra with @VedantKhairnar
• Reimagined flow to be made with PT

[MohitNSamagra]

• Testing pending

[MohitNSamagra]

• @MohitNSamagra @VedantKhairnar - to be picked on wed

[MohitNSamagra]

Open questions:

1. What happens if all questions are not answered within role assignment?(dev req?)
2. Where is role assignment data being stored? only gender being stored in contributors_discord(dev req?)
3. PR to be reviewed by @KDwevedi @karntrehan

[VedantKhairnar]

PR Info:

• Once authorization is done, RoleID1(Verified Contributor) is assigned which unlocks all the channels
• Now, what we want is, the authorization instead of unlocking all channels, unlocks only 1 channel(#roles) by assigning the RoleId2 instead of RoleID1 and activity on the #roles channel will assign the #roleID1 which will unlock all the channels
• Above is done by the PR
• Ignore the names verified contributor and community member as later we will swap the names but roleID stays the same

[MohitNSamagra]

Issue to be resolved

• dynobot not able to manage roles

[MohitNSamagra]

• Call with Parth @VedantKhairnar this week(by Thurs)

[MohitNSamagra]

@MohitNSamagra @VedantKhairnar to connect and update

[MohitNSamagra]

• Opening channels based on answer to last question(without dev, confirmed)
• Other onboarding data to be stored in db as well
• Questions should be made customisable - dev effort to be discussed with @karntrehan
• PR to be merged post this

[MohitNSamagra]

• @jaanbaaz to review existing code for db changes
• @karntrehan to review in 2416

[MohitNSamagra]

moved to https://github.com/orgs/Code4GovTech/projects/1/views/2?pane=issue&itemId=70454796