github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #476] [Feature Request]: Surpress welcome modal when budget exists. #14399

New Issue
Closed
opened 2026-04-14 17:07:34 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-04-14 17:07:34 -05:00
Owner
Copy Link

Originally created by @rich-howell on GitHub (Jan 17, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/476

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

I would like the ability to be able to disable the welcome to actual modal that appears when you login to Actual on a new device. If I had an active budget already configured and I log in on a new device don't show me the welcome modal.

Originally created by @rich-howell on GitHub (Jan 17, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/476 ### Verified issue does not already exist? I have searched and found no existing issue ### What happened? I would like the ability to be able to disable the welcome to actual modal that appears when you login to Actual on a new device. If I had an active budget already configured and I log in on a new device don't show me the welcome modal.
GiteaMirror added the user interfacegood first issuehelp wanted labels 2026-04-14 17:07:34 -05:00
GiteaMirror commented 2026-04-14 17:07:35 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jan 17, 2023):

There are a couple of ways to approach this:

  • check if you have any accounts before showing the dialog, and skip it if you do. Pro: guarantees you’ll never see the dialog again after you start using Actual. Con: people who start by importing a budget from YNAB/elsewhere won’t see the welcome dialog. Also requires some code changes to load the list of accounts before attempting to show the dialog.
  • save both a per-browser and per-file setting for if you’ve seen the dialog, and propagate them to each other if one is true. Pro: first time users will always see the dialog if they start by creating/importing a budget. Con: if multiple people use the same budget, only one will see the dialog. Also, if you ever open a budget from someone else you will miss out on the dialog.
<!-- gh-comment-id:1386009297 --> @j-f1 commented on GitHub (Jan 17, 2023): There are a couple of ways to approach this: - check if you have any accounts before showing the dialog, and skip it if you do. **Pro**: guarantees you’ll never see the dialog again after you start using Actual. **Con**: people who start by importing a budget from YNAB/elsewhere won’t see the welcome dialog. Also requires some code changes to load the list of accounts before attempting to show the dialog. - save both a per-browser and per-file setting for if you’ve seen the dialog, and propagate them to each other if one is `true`. **Pro**: first time users will always see the dialog if they start by creating/importing a budget. **Con**: if multiple people use the same budget, only one will see the dialog. Also, if you ever open a budget from someone else you will miss out on the dialog.
GiteaMirror commented 2026-04-14 17:07:36 -05:00
Author
Owner
Copy Link

@4-Leafs-Code commented on GitHub (Jan 21, 2023):

What about saving a list of users per budget in the database and just cross-referencing to the user to the list. This way if the user has been welcomed he will not be again no mater what device or browser they log in from but if they access a different budget they would be welcomed. Also, if multiple user are accessing the same budget then they would all be welcomed only once for that budget. I do not know your code or what Database you are using but this is similar to "likes counter" we made for out post.

I think this solve your "con" concerns but that on my assumption that you have a user data base with login capabilities. I hope this helps.

<!-- gh-comment-id:1399228045 --> @4-Leafs-Code commented on GitHub (Jan 21, 2023): What about saving a list of users per budget in the database and just cross-referencing to the user to the list. This way if the user has been welcomed he will not be again no mater what device or browser they log in from but if they access a different budget they would be welcomed. Also, if multiple user are accessing the same budget then they would all be welcomed only once for that budget. I do not know your code or what Database you are using but this is similar to "likes counter" we made for out post. I think this solve your "con" concerns but that on my assumption that you have a user data base with login capabilities. I hope this helps.
GiteaMirror commented 2026-04-14 17:07:36 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Jan 21, 2023):

We don’t really have multiple users at this point (since there’s just one password for the server) but that could be an interesting future direction!

<!-- gh-comment-id:1399235389 --> @j-f1 commented on GitHub (Jan 21, 2023): We don’t really have multiple users at this point (since there’s just one password for the server) but that could be an interesting future direction!
GiteaMirror commented 2026-04-14 17:07:36 -05:00
Author
Owner
Copy Link

@4-Leafs-Code commented on GitHub (Jan 21, 2023):

Okay so another option is have the user sign in with a simple screen name like First.LastNames while your user base is small and set the list up so the user will only see the welcome screen 1 time when they set up their screen name and in the future when your user base grows move the welcome list validation to each of the budgets and off from the login.

<!-- gh-comment-id:1399245037 --> @4-Leafs-Code commented on GitHub (Jan 21, 2023): Okay so another option is have the user sign in with a simple screen name like First.LastNames while your user base is small and set the list up so the user will only see the welcome screen 1 time when they set up their screen name and in the future when your user base grows move the welcome list validation to each of the budgets and off from the login.
GiteaMirror commented 2026-04-14 17:07:37 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Mar 30, 2023):

Jed has recently done some changes to the onboarding workflow and we no longer have the welcome modal. So this is done :)

<!-- gh-comment-id:1490838741 --> @MatissJanis commented on GitHub (Mar 30, 2023): Jed has recently done some changes to the onboarding workflow and we no longer have the welcome modal. So this is done :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label good first issue help wanted user interface
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#14399
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?