Feature request for SlackBot

The problem.

1. Chrome can save usernames and passwords. Chrome can't handle many usernames associated with the Qlearsite domain. Chrome usernames confusion persists during urgent tasks connected with access needed while no one can afford time for help.

2. I face up the log in issue despite password reset working properly due to usage of lots of test users on the same email or my Qlearsite account was created without a negotiation about desirable Username.

3. Some users can not manage their usernames through all the Qlearsite instances.

What other ways did I try to solve your problem?

• Creating own doc for everyone to keep their passwords and usernames.

• Using several browsers.

The solution. My vision.

Where applicable: SlackBot.

Opportunity Statement: This is the right time to widen SlackBot functionality mentioned as "Pulling out all the usernames from the instance"

Link to examples and research:

https://qlearsite.atlassian.net/browse/TECHOPS-303

Key objectives:

Sometimes there is no opportunity to disturb teammates who already have accounts on the instance I need for them to check what my username is. I came up with the idea that we can send the SlackBot estimated email and the desired instance link while SlackBot will respond with options like:

• /: There is no Username associated with this email. You can use /legacy-create-user command.

• /: Your Username on <instance name> is: <username>

Optional objectives:

.xlsx file export to the email provider for an easy search of username associated with his(her) account.

Key Audience:

•Support team

•QA team

•PM team

Date Requested: 31.10.2019

Request participants: Oleg Plyska; Daphne P. William S.

Original Requestor(s): Maksym Dodon

Contact name: maksym.dodon@qlearsite.com

Area of request: SlackBot(ios) SlackBot(desktop)

My feature request typically stems from a selfish need: Yes, something that I feel should change to benefit my app usage. And, this may be very subjective - what I think might be a feature, others could consider a drawback. Therefore feature requests should have a far bigger scope than just Oleg. Have that in mind when considering my request.