84 lines
4.3 KiB
Markdown
84 lines
4.3 KiB
Markdown
# Humly
|
|
|
|
## 6/21/2022
|
|
|
|
### Technical People
|
|
|
|
- Tomasz (Tom) - Client and Team Leader
|
|
- Bartosz - Full stack developer, 2 years at Humly
|
|
|
|
### Answers to Questions from email
|
|
How do we know what courses a candidate has completed? Should we store it ourselves or should we always get it from Northpass? What is the best practice?
|
|
- They want to apply some logic to these completions in Northpass
|
|
- This is for the recruitment part, so they need to complete
|
|
-
|
|
|
|
We want to learn more about where the logic to decide which user that gets which course lives - is that in Northpass or in Humly? If in Northpass, how does that work? Can we pass any data into that logic and then set up the rules ourselves in Northpass?
|
|
- UUIDs for groups
|
|
- Mapping group creation from Humly
|
|
-
|
|
We plan to use your token or signature-based authentication and might have some questions about it, not sure yet.
|
|
- [X] Send token based authentication PDFs
|
|
General best practices on how to use the development resources and work with the technical aspects with Northpass. Any risks that we should avoid when designing the technical solution?
|
|
- Be specific
|
|
We plan to just link to Northpass and open it in a separate browser to start with - but how would it work if we want to include the courses and pieces of training in our app experience in the future? Do you have frontend components for the courses we can use or do we need to write everything ourselves?
|
|
- What is front end components?
|
|
- Lyft Example
|
|
- Ludvig is working on the design
|
|
- They might want to show
|
|
|
|
Status is they are mapping out and deciding what Northpass involvment should be
|
|
|
|
|
|
## 10/05/2022
|
|
* Candidate should go into app and complete training and courses in NP
|
|
* How to setup rules? Where?
|
|
* Linda understood this was done in Hubspot
|
|
* We need to figure out where all the data is that decide their final destination/course
|
|
* Hubspot is a mirror of Humly backend
|
|
* Hubspot workflows are important
|
|
* Hubspot brings power to the Talent Success team
|
|
* Linda's concern is if it is built in the back office, it will take up too much time
|
|
* Example:
|
|
* New applicant in back office
|
|
* They would be created in Hubspot
|
|
* THey want to offer one introduction training depending on region
|
|
* Hampshire vs Milton-?
|
|
* Hubspot will have all the correct attributes
|
|
* Process - onboarding & then other processes and flows
|
|
* Not fully understanding emails and enrollments with Hubspot workflows
|
|
* There is a concern of misunderstanding
|
|
* P asking about the variables that play into what courses should be administered
|
|
* Region is one. They may want to send courses to people who haven't or have worked etc.
|
|
* Turn off Hubspot integration!!
|
|
* They want Humly to be the SST and data should go to Northpass > Humly > Hubspot
|
|
* Webhooks are the best way to catch information in Humly
|
|
* API will be more for group or person information.
|
|
* Kristoffer said something about messy user experience
|
|
* Was something miscommunicated in sales? Linda not understanding segmentation vs enrollment vs communications
|
|
* Kristoffer's example was can Mika create a group based on x number of deviations within Hubspot/Humly
|
|
* But why would we create the group first in Northpass? There's not logic in Northpass group creation
|
|
* Patrycja gave example of using JS to run script to look for information in Humly app.
|
|
* Linda suggesting that Northpass needs to know "know everything"?
|
|
* Oskar asking - could we tell Hubspot to tell Northpass which users are part of a group?
|
|
* Oskar rightly saying that Hubspot integration is just a link provider, it just allows for prettier emails
|
|
* To summarize, they need to rethink about their data flow
|
|
* Miro for workflow diagram for user and data.
|
|
|
|
## 10/06/2022
|
|
* Course Title should be bigger in LX
|
|
* Okay to change across all courses
|
|
* Title font size 30
|
|
* Flow: Intro course > Interview > 5-6 Courses (all in the app) > Offer to be a Teeacher
|
|
* Those 5-6 courses _should_ be done in order, but its not necessary
|
|
* A few quizzes across the 5-6 courses
|
|
|
|
# Feature Requests
|
|
|**Request**|**Date** | **Product/PM** |
|
|
|---------|------|------------|
|
|
|Learning path organization | 9/8/22 | Marta |
|
|
|Enroll people in courses from Hubspot. Not just communicate | 10/5/22 | Partners Team |
|
|
| Title of Course should be RTE | 10/6/2022 | LX Team |
|
|
|
|
|--|--|--|
|