github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[Feature] Separate Simplefin / banking info per user or OpenID. #2519

New Issue
Closed
opened 2026-02-28 20:16:51 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 20:16:51 -06:00
Owner
Copy Link

Originally created by @nathanxpereira on GitHub (Oct 5, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

Currently across all users, only one Simplefin account can be used. Meaning every user (if admin role) has access to pull accounts from that simplefin. In a scenario where hosting multiple users, ideally, banking information should be kept separate for privacy. Without this in place, there is no point in having multiple users, unless the admin strictly regulates what accounts get used in each account.

Describe your ideal solution to this problem

Each user should have their own simplefin account/ info. This could be linked per email or OpenID sign in. Separating this information is key to privacy.

See this as a related issue: https://github.com/actualbudget/actual/issues/5550

Teaching and learning

The current front end features and documentation would largely remain the same. There would still be the same bank linking methods, but it should be noted within the documentation that this only pertains to the user. I imagine this would provide more clarity on the usage of actual budget in a multi-user scenario.

Originally created by @nathanxpereira on GitHub (Oct 5, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Currently across all users, only one Simplefin account can be used. Meaning every user (if admin role) has access to pull accounts from that simplefin. In a scenario where hosting multiple users, ideally, banking information should be kept separate for privacy. Without this in place, there is no point in having multiple users, unless the admin strictly regulates what accounts get used in each account. ### Describe your ideal solution to this problem Each user should have their own simplefin account/ info. This could be linked per email or OpenID sign in. Separating this information is key to privacy. See this as a related issue: https://github.com/actualbudget/actual/issues/5550 ### Teaching and learning The current front end features and documentation would largely remain the same. There would still be the same bank linking methods, but it should be noted within the documentation that this only pertains to the user. I imagine this would provide more clarity on the usage of actual budget in a multi-user scenario.
GiteaMirror added the needs votesfeature labels 2026-02-28 20:16:51 -06:00
GiteaMirror commented 2026-02-28 20:16:52 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 5, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Oct 5, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label feature needs votes
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#2519
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?