Add Merge Account to NewExpensify #47073
Comments
zanyrenney
added
Daily
|
Current assignees @twisterdotcom and @zanyrenney are eligible for the NewFeature assigner, not assigning anyone new. |
|
|
|
Triggered auto assignment to Design team member for new feature review - @dannymcclain ( |
|
Edited by proposal-police: This proposal was edited at 2024-08-19 15:59:41 UTC. Need to improve this but startign with the P/S Proposal: add the remaining account settings to new dot, Part 1: Merge Account (Part 2: Device Management TBC)Problem:When users accidentally create personal accounts while their company is using Expensify, they face several issues. They must either:
Generally, users can’t share reports directly with their company in-app, and managing two accounts can be confusing. Users might also unknowingly create expenses that don't align with company policies. Solution:Rebuild the ability to "Merge Accounts" in NewExpensify. This feature allows users to easily merge their personal and company accounts on Expensify. This will improve the transfer from individual expense data to company-created accounts, giving visibility to admins and mitigating the need to create a novel account for those originally creating individual accounts. |
|
Pre-design on merging accounts for workspace feed/card conversation: https://expensify.slack.com/archives/C036QM0SLJK/p1723841346915409 |
Proposal: Add the remaining account settings to NewExpensify.Part 1: Merge Account Problem:When users accidentally create personal accounts while their company is using Expensify, they face several issues. They must either:
Generally, users can’t share reports directly with their company in-app, and managing two accounts can be confusing. Users might also unknowingly create expenses that don't align with company policies. Solution:Rebuild the ability to "Merge Accounts" in NewExpensify. This feature allows users to easily merge their personal and company accounts on Expensify. This will improve the transfer from individual expense data to company-created accounts, giving visibility to admins and mitigating the need to create a novel account for those originally creating individual accounts, and crucially, give them the ability to do take this action without requiring access to Expensify Classic. |
|
@zanyrenney Your proposal will be dismissed because you did not follow the proposal template. |
|
This is a bit mean, I haven't even done it yet 🥲 |
|
Not sure we need @dannymcclain here yet so will remove this from clogging up his K2. |
|
|
|
@twisterdotcom and I considered getting the pre-design out today or tomorrow but I realised we need to email strat@ prior, so done that and then can get the pre-design in flight! |
|
Back from some OOO. @zanyrenney has been predesigning in a canvas in my absence. |
|
pre-design is posted! https://expensify.slack.com/archives/C06ML6X0W9L/p1725276863731789 |
|
okay think data storage / api changes is all set for now, at least I've tried to document where I wasn't sure and can hopefully get the feedback from the team then to get to the right spot. I resolved the rest of the outstanding items i had open and left some suggestions for @zanyrenney on that last remaining question you'd tagged me in. I think we're in a good spot to send it out once you review those suggestions. |
|
woooo! |
zanyrenney
added
DesignDocReview
|
shipped! |
|
I have read and reviewed this Design Doc! |
2 similar comments
|
I have read and reviewed this Design Doc! |
|
I have read and reviewed this Design Doc! |
|
I have read and reviewed this Design Doc! |
1 similar comment
|
I have read and reviewed this Design Doc! |
|
doc is in review and comments are being addressed |
|
Same as Friday. It's in review. |
|
I have read and reviewed this Design Doc! |
DESIGN DOC ➡️
Proposal
Tasks
#whatsnextstrategy@expensify.comand paste in the Proposalstrategy@expensify.com(continue the same email chain as before - your last message should be the WN Proposal) with the link to your Design Doc containing your high-level problem and solutionDesignDocReviewlabel to get the High-level overview of the problem and High-level of proposed solution section reviewedDesignDocReviewlabel to this issuestrategy@expensify.comone last time to let them know the Design Doc is moving into the implementation phasestrategy@expensify.comonce everything has been implemented and do a Project Wrap-Up retrospective that provides:The text was updated successfully, but these errors were encountered: