github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 04:02:38 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Allow automated creation of user accounts when using OpenID #2316

New Issue
Closed
opened 2026-02-28 20:10:16 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 20:10:16 -06:00
Owner
Copy Link

Originally created by @jsmith212 on GitHub (Jul 27, 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, even in an SSO-focused environment, users must first be manually created in Actual Budget before they can log in. This involves an extra provisioning step for new users.

Describe your ideal solution to this problem

The ideal solution, and the one employed by many others, is to automatically create the user if it does not already exist when they first attempt to log in. As a stretch goal, this can be restricted through the use of groups, but it isn't mandatory since this can also be enforced through proxy (or k8s ingress) access control lists.

This would probably be good to have in the config file and environment variables, and disabled by default.

Teaching and learning

This is one of those quiet QoL improvements that just happens under the hood, if enabled, but makes a big difference for admins, especially with a decent number of users. Being able to just create the user in the backing LDAP service, add them to a group, and have things "just work" is really nice.

Originally created by @jsmith212 on GitHub (Jul 27, 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, even in an SSO-focused environment, users must first be manually created in Actual Budget before they can log in. This involves an extra provisioning step for new users. ### Describe your ideal solution to this problem The ideal solution, and the one employed by many others, is to automatically create the user if it does not already exist when they first attempt to log in. As a stretch goal, this can be restricted through the use of groups, but it isn't mandatory since this can also be enforced through proxy (or k8s ingress) access control lists. This would probably be good to have in the config file and environment variables, and disabled by default. ### Teaching and learning This is one of those quiet QoL improvements that just happens under the hood, if enabled, but makes a big difference for admins, especially with a decent number of users. Being able to just create the user in the backing LDAP service, add them to a group, and have things "just work" is really nice.
GiteaMirror added the feature label 2026-02-28 20:10:16 -06:00
GiteaMirror commented 2026-02-28 20:10:17 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 27, 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 (Jul 27, 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 -->
GiteaMirror commented 2026-02-28 20:10:17 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Sep 2, 2025):

closing in favor of #5469

@youngcw commented on GitHub (Sep 2, 2025): closing in favor of #5469
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 feature
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#2316
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?