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

[GH-ISSUE #5177] [Bug]: Account privacy #79643

New Issue
Closed
opened 2026-05-19 02:42:54 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-05-19 02:42:54 -05:00
Owner
Copy Link

Originally created by @mark-kazakov on GitHub (Jun 16, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5177

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Account privacy settings

Hi everyone,
Thanks for this great app, I am currently discovering it.
I have setup it up with OpenID connect with multiple users.

I was expecting users to have private spaces for there accounts.
But I found out that when a user creates an account, the account is accessible to other uers, as well as the balance to everyone who has access to that instance.

To me this is an issue, since I guess not all users want to share there account details with other users.
I still think that there must be a way to share accounts across, either groups or users.

This issue is similar to #1041 but I think the issue is not only the balance, but users must have ability to set account as public, and the default behavior should be private.

How can we reproduce the issue?

How can we reproduce the issue?

  1. instance with OpenID
  2. Login with user A (owner or not)
  3. Create an account (called XXX)
  4. login with user B (owner or not)
  5. now the account (XXX) created by user A is visible by user B

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @mark-kazakov on GitHub (Jun 16, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5177 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? # Account privacy settings Hi everyone, Thanks for this great app, I am currently discovering it. I have setup it up with OpenID connect with multiple users. I was expecting users to have private spaces for there accounts. But I found out that when a user creates an account, the account is accessible to other uers, as well as the balance to everyone who has access to that instance. To me this is an issue, since I guess not all users want to share there account details with other users. I still think that there must be a way to share accounts across, either groups or users. This issue is similar to #1041 but I think the issue is not only the balance, but users must have ability to set account as public, and the default behavior should be private. ### How can we reproduce the issue? ## How can we reproduce the issue? 1. instance with OpenID 2. Login with user A (owner or not) 3. Create an account (called XXX) 4. login with user B (owner or not) 5. now the account (XXX) created by user A is visible by user B ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bugneeds info labels 2026-05-19 02:42:54 -05:00
GiteaMirror commented 2026-05-19 02:42:58 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jun 16, 2025):

Do you mean like within a budget file? If a user wants to keep their data private, make a new budget file. If the owner of a file shares that file with other users, then everything in that file is available to the shared user(s).

<!-- gh-comment-id:2978428265 --> @youngcw commented on GitHub (Jun 16, 2025): Do you mean like within a budget file? If a user wants to keep their data private, make a new budget file. If the owner of a file shares that file with other users, then everything in that file is available to the shared user(s).
GiteaMirror commented 2026-05-19 02:43:01 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jul 9, 2025):

closing because of no response

<!-- gh-comment-id:3050961538 --> @youngcw commented on GitHub (Jul 9, 2025): closing because of no response
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 bug needs info
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#79643
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?