github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-11-12 03:42:19 -06:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #8014] [Feature] Per-User Bank Sync Connections or Granular Bank Sync Permissions #117642

New Issue
Closed
opened 2026-06-11 13:04:40 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-06-11 13:04:40 -05:00
Owner
Copy Link
Copy Source

Originally created by @jsaltzman on GitHub (May 31, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/8014

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?

In a multi-user setup, non-admin (Basic role) users are blocked from linking accounts to bank sync providers like SimpleFIN with the error: "You don't have the required permissions to set up secrets. Please contact an Admin to configure GoCardless or Pluggy.ai."

This means that even when an admin has already configured SimpleFIN on the server, a Basic user cannot link their own accounts — forcing the admin to either:

  • Temporarily promote the user to Admin (a security concern)
  • Link the accounts on their behalf (a privacy concern and operational burden)

This is a significant barrier for households or small teams where multiple people manage separate budgets on the same Actual server.

Describe your ideal solution to this problem

One or both of the following approaches would address this:

Option A: Per-User SimpleFIN Connections
Allow each user to configure their own SimpleFIN token independently, scoped to their account only. This keeps bank credentials isolated per user and doesn't require any admin involvement.

Option B: Granular Bank Sync Permission
Introduce a fine-grained permission (separate from the full Admin role) that allows specific Basic users to use the server's pre-configured bank sync secrets to link their own accounts — without granting them full admin privileges.

Why This Matters

The multi-user feature is designed for shared server deployments. Bank sync is one of Actual's most valuable features. Requiring admin access just to link accounts undermines the usability of both features together. The secrets are already on the server — Basic users shouldn't need elevated privileges just to use them.

Workarounds Today

  • Admin links accounts on behalf of users (privacy concern)
  • Temporarily promote user to Admin, link, then demote (cumbersome and risky)

Neither is a good long-term solution for a multi-user household or team setup.

Teaching and learning

Documentation added to the SimpleFin page explaining the per-user granular permissions or per-user syncing.

Originally created by @jsaltzman on GitHub (May 31, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/8014 ### 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? In a multi-user setup, non-admin (Basic role) users are blocked from linking accounts to bank sync providers like SimpleFIN with the error: *"You don't have the required permissions to set up secrets. Please contact an Admin to configure GoCardless or Pluggy.ai."* This means that even when an admin has already configured SimpleFIN on the server, a Basic user cannot link their own accounts — forcing the admin to either: - Temporarily promote the user to Admin (a security concern) - Link the accounts on their behalf (a privacy concern and operational burden) This is a significant barrier for households or small teams where multiple people manage separate budgets on the same Actual server. ### Describe your ideal solution to this problem One or both of the following approaches would address this: **Option A: Per-User SimpleFIN Connections** Allow each user to configure their own SimpleFIN token independently, scoped to their account only. This keeps bank credentials isolated per user and doesn't require any admin involvement. **Option B: Granular Bank Sync Permission** Introduce a fine-grained permission (separate from the full Admin role) that allows specific Basic users to use the server's pre-configured bank sync secrets to link their own accounts — without granting them full admin privileges. ### Why This Matters The multi-user feature is designed for shared server deployments. Bank sync is one of Actual's most valuable features. Requiring admin access just to link accounts undermines the usability of both features together. The secrets are already on the server — Basic users shouldn't need elevated privileges just to use them. ### Workarounds Today - Admin links accounts on behalf of users (privacy concern) - Temporarily promote user to Admin, link, then demote (cumbersome and risky) Neither is a good long-term solution for a multi-user household or team setup. ### Teaching and learning Documentation added to the SimpleFin page explaining the per-user granular permissions or per-user syncing.
GiteaMirror added the featureneeds votes labels 2026-06-11 13:04:41 -05:00
GiteaMirror commented 2026-06-11 13:04:43 -05:00
Author
Owner
Copy Link
Copy Source

@github-actions[bot] commented on GitHub (May 31, 2026):

✨ 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 👍!

<!-- gh-comment-id:4588283573 --> @github-actions[bot] commented on GitHub (May 31, 2026): :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 -->
GiteaMirror commented 2026-06-11 13:04:43 -05:00
Author
Owner
Copy Link
Copy Source

@coderabbitai[bot] commented on GitHub (May 31, 2026):

⚠️ Possible Duplicate Issue(s)
📝 Issue Planner

Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

  • Create Plan
🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

<!-- gh-comment-id:4588290670 --> @coderabbitai[bot] commented on GitHub (May 31, 2026): <!-- This is an auto-generated issue plan by CodeRabbit --> <details> <summary>⚠️ Possible Duplicate Issue(s)</summary> - https://github.com/actualbudget/actual/issues/5859 </details> --- <details> <summary>📝 Issue Planner</summary> <sub>Check the box below or use the `@coderabbitai plan` command to generate an implementation plan and prompts that you can use with your favorite coding assistant.</sub> - [ ] <!-- {"checkboxId": "8d4f2b9c-3e1a-4f7c-a9b2-d5e8f1c4a7b9"} --> Create Plan </details> --- <details> <summary> 🧪 Issue enrichment is currently in open beta.</summary> You can configure auto-planning by selecting labels in the issue_enrichment configuration. To disable automatic issue enrichment, add the following to your `.coderabbit.yaml`: ```yaml issue_enrichment: auto_enrich: enabled: false ``` </details> 💬 Have feedback or questions? Drop into our [discord](https://discord.gg/coderabbit)!
GiteaMirror commented 2026-06-11 13:04:43 -05:00
Author
Owner
Copy Link
Copy Source

@jsaltzman commented on GitHub (May 31, 2026):

This is very similar to https://github.com/actualbudget/actual/issues/5859 but I would note that I think my suggestion for fine-grained control to who can access certain SimpleFin links is novel.

<!-- gh-comment-id:4588322645 --> @jsaltzman commented on GitHub (May 31, 2026): This is very similar to https://github.com/actualbudget/actual/issues/5859 but I would note that I think my suggestion for fine-grained control to who can access certain SimpleFin links is novel.
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 labels feature needs votes
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
GiteaMirror ninjasurge (Kaehlen Rog)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117642