[GH-ISSUE #524] [Feature] Add user support to Actual #41856

New Issue

GiteaMirror · 2026-04-26T01:18:26-05:00

GiteaMirror commented

2026-04-26 01:18:26 -05:00

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

Discussed in https://github.com/actualbudget/actual/discussions/157

^{Originally posted by winklevos August 6, 2022}
User enhancements
- User sign-in support
- Multiple users per server support
- Shared access to account support

Originally created by @rich-howell on GitHub (Jan 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/524 ### Discussed in https://github.com/actualbudget/actual/discussions/157 <div type='discussions-op-text'> <sup>Originally posted by **winklevos** August 6, 2022</sup> User enhancements - User sign-in support - Multiple users per server support - Shared access to account support</div>

GiteaMirror added the feature label 2026-04-26 01:18:26 -05:00

GiteaMirror closed this issue

2026-04-26 01:18:27 -05:00

GiteaMirror commented

2026-04-26 01:18:28 -05:00

@rich-howell commented on GitHub (Jan 28, 2023):

Discussed in https://github.com/actualbudget/actual/discussions/123

Originally posted by Quigley-Brendan July 5, 2022
I was one of those YNAB people who got their friends and family using YNAB. After a few price increases etc I'm finding it harder to recommend. But I could totally self-host an Actual Server (just found this app the other day). If accounts could be enabled on the server I could give the people in my circle their own account, potentially saving them a bit each year on the YNAB referral.

Any plans to make this happen?

@rich-howell commented on GitHub (Jan 28, 2023): Discussed in https://github.com/actualbudget/actual/discussions/123 Originally posted by Quigley-Brendan July 5, 2022 I was one of those YNAB people who got their friends and family using YNAB. After a few price increases etc I'm finding it harder to recommend. But I could totally self-host an Actual Server (just found this app the other day). If accounts could be enabled on the server I could give the people in my circle their own account, potentially saving them a bit each year on the YNAB referral. Any plans to make this happen?

GiteaMirror commented

2026-04-26 01:18:29 -05:00

@tjex commented on GitHub (Mar 21, 2023):

Was thinking about an alternate solution for implementing multi-user login based on what is currently available.

Considering there is already per budget file encryption enabled, could it be an option to share the same login to the server instance, but instead of being presented with all budgets, the user would need to input their password for their encrypted budget file/s.

All budgets that match that password, could then be shown and subsequently opened.

This might be smoother to implement than multi user server login?

@tjex commented on GitHub (Mar 21, 2023): Was thinking about an alternate solution for implementing multi-user login based on what is currently available. Considering there is already per budget file encryption enabled, could it be an option to share the same login to the server instance, but instead of being presented with all budgets, the user would need to input their password for their encrypted budget file/s. All budgets that match that password, could then be shown and subsequently opened. This might be smoother to implement than multi user server login?

GiteaMirror commented

2026-04-26 01:18:30 -05:00

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

That’s a good idea! Thinking about how that would work, we’d fetch all of the encrypted keys from the server, then try the password against all of them. I’m not sure if there would be a way for us to grant access to only the budgets encrypted with a given key in the backend since there isn’t exactly a way to prove that we can decrypt that key. But I think that’s definitely a good approach to investigate more!

@j-f1 commented on GitHub (Mar 21, 2023): That’s a good idea! Thinking about how that would work, we’d fetch all of the encrypted keys from the server, then try the password against all of them. I’m not sure if there would be a way for us to grant access to only the budgets encrypted with a given key in the backend since there isn’t exactly a way to prove that we can decrypt that key. But I think that’s definitely a good approach to investigate more!

GiteaMirror commented

2026-04-26 01:18:31 -05:00

@github-actions[bot] commented on GitHub (May 1, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 (May 1, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!

GiteaMirror commented

2026-04-26 01:18:31 -05:00

@imjuniper commented on GitHub (Jul 12, 2023):

@j-f1 I haven't checked how the backend works at all (very new to Actual Budget), but considering the encryption keys are in a database already, couldn't it be possible to add a table to know which key is related to which file? Or it could also just use multiple databases, just split into subfolders according to the username (i.e. username/account.sqlite).

@imjuniper commented on GitHub (Jul 12, 2023): @j-f1 I haven't checked how the backend works at all (very new to Actual Budget), but considering the encryption keys are in a database already, couldn't it be possible to add a table to know which key is related to which file? Or it could also just use multiple databases, just split into subfolders according to the username (i.e. `username/account.sqlite`).

GiteaMirror commented

2026-04-26 01:18:32 -05:00

@Scot-Survivor commented on GitHub (Jul 12, 2023):

I'm surprised the demand for this isn't higher. With those with families. It would be brilliant to have a little raspberry pi hosting actual for the whole family to be able to use (and safely, without worrying about other family members)

Shared files allowing to budget with roommates or partners.

And obviously the fact that not everyone has the ability to set this up, but the chances are they have a nerdy friend who can, but having to setup 1 server (and this subdomain) per user is more work than it's worth to say the least.

Is there a branch or current PR where this is being worked on, I'd love to help out.

@Scot-Survivor commented on GitHub (Jul 12, 2023): I'm surprised the demand for this isn't higher. With those with families. It would be brilliant to have a little raspberry pi hosting actual for the whole family to be able to use (and safely, without worrying about other family members) Shared files allowing to budget with roommates or partners. And obviously the fact that not everyone has the ability to set this up, but the chances are they have a nerdy friend who can, but having to setup 1 server (and this subdomain) per user is more work than it's worth to say the least. Is there a branch or current PR where this is being worked on, I'd love to help out.

GiteaMirror commented

2026-04-26 01:18:33 -05:00

@j-f1 commented on GitHub (Jul 12, 2023):

@jakobbouchard We already store separate encryption keys for every file that has encryption enabled (it’s optional).

@j-f1 commented on GitHub (Jul 12, 2023): @jakobbouchard We already store separate encryption keys for every file that has encryption enabled (it’s optional).

GiteaMirror commented

2026-04-26 01:18:33 -05:00

@j-f1 commented on GitHub (Jul 12, 2023):

@Scot-Survivor I don’t know of anyone working on this at the moment, but feel free to pitch your idea for how this would work!

@j-f1 commented on GitHub (Jul 12, 2023): @Scot-Survivor I don’t know of anyone working on this at the moment, but feel free to pitch your idea for how this would work!

GiteaMirror commented

2026-04-26 01:18:34 -05:00

@j-f1 commented on GitHub (Jul 12, 2023):

Potentially relevant: https://github.com/actualbudget/actual-server/pull/219 (we hope to merge that PR soon)

@j-f1 commented on GitHub (Jul 12, 2023): Potentially relevant: https://github.com/actualbudget/actual-server/pull/219 (we hope to merge that PR soon)

GiteaMirror commented

2026-04-26 01:18:35 -05:00

@Scot-Survivor commented on GitHub (Jul 12, 2023):

Just pulling the discussion from Discord, as per @j-f1 , it would be possible to add a username field when logging, and only serve the associated files to that user.
However, some additional things would be required:

Admin Account (and management?)
Admin Dashboard (Reset user passwords, remove users, add users?)
And then from me myself I'd like to see:
See stats, such as storage per user.
Enforce End to End Encryption.
Enforce 2FA on the admin (this should probably be added for all users, I think I saw an issue with this?)

Does anyone else see something I'm missing?

@Scot-Survivor commented on GitHub (Jul 12, 2023): Just pulling the discussion from Discord, as per @j-f1 , it would be possible to add a username field when logging, and only serve the associated files to that user. However, some additional things would be required: - Admin Account (and management?) - Admin Dashboard (Reset user passwords, remove users, add users?) And then from me myself I'd like to see: - See stats, such as storage per user. - Enforce End to End Encryption. - Enforce 2FA on the admin (this should probably be added for all users, I think I saw an issue with this?) Does anyone else see something I'm missing?

GiteaMirror commented

2026-04-26 01:18:35 -05:00

@j-f1 commented on GitHub (Jul 12, 2023):

Seems reasonable except for the 2FA bit — would like to see use of passkeys instead of requiring more complex security measures if possible.

@j-f1 commented on GitHub (Jul 12, 2023): Seems reasonable except for the 2FA bit — would like to see use of passkeys instead of requiring more complex security measures if possible.

GiteaMirror commented

2026-04-26 01:18:36 -05:00

@Scot-Survivor commented on GitHub (Jul 12, 2023):

True, if I recall correctly there's a library that can handle both 2FA & Passkeys, I personally don't own a pass key so I'm left with having to use 2FA codes.

@Scot-Survivor commented on GitHub (Jul 12, 2023): True, if I recall correctly there's a library that can handle both 2FA & Passkeys, I personally don't own a pass key so I'm left with having to use 2FA codes.

GiteaMirror commented

2026-04-26 01:18:37 -05:00

@Gandalf-the-Blue commented on GitHub (Aug 13, 2023):

I am currently sharing my instance of Actual with my sister. We use the same password for logging in but then have our separate budget files, E2E encrypted. The only problem I see with this setup is either user can delete the others' file without problem. If a temporary fix to input the E2E password before deleting a file is added it would solve this issue at least temporarily.

@Gandalf-the-Blue commented on GitHub (Aug 13, 2023): I am currently sharing my instance of Actual with my sister. We use the same password for logging in but then have our separate budget files, E2E encrypted. The only problem I see with this setup is either user can delete the others' file without problem. If a temporary fix to input the E2E password before deleting a file is added it would solve this issue at least temporarily.

GiteaMirror commented

2026-04-26 01:18:38 -05:00

@Scot-Survivor commented on GitHub (Aug 19, 2023):

Is there anyone working on this at the moment?

@Scot-Survivor commented on GitHub (Aug 19, 2023): Is there anyone working on this at the moment?

GiteaMirror commented

2026-04-26 01:18:38 -05:00

@barart commented on GitHub (Feb 7, 2024):

+1 on this, i do not want to create a new docker instance for each member of my family

@barart commented on GitHub (Feb 7, 2024): +1 on this, i do not want to create a new docker instance for each member of my family

GiteaMirror commented

2026-04-26 01:18:39 -05:00

@akshay7394 commented on GitHub (Mar 29, 2024):

+1 on this from me too

@akshay7394 commented on GitHub (Mar 29, 2024): +1 on this from me too

GiteaMirror commented

2026-04-26 01:18:39 -05:00

@S4GU4R0 commented on GitHub (Apr 5, 2024):

This has the second most upvotes outside of Plaid integration. When perusing other feature requests with less votes, there are tasks done. Is it possible to get an update and some clarification on this? Thank you.

@S4GU4R0 commented on GitHub (Apr 5, 2024): This has the second most upvotes outside of Plaid integration. When perusing other feature requests with less votes, there are tasks done. Is it possible to get an update and some clarification on this? Thank you.

GiteaMirror commented

2026-04-26 01:18:40 -05:00

@rich-howell commented on GitHub (Apr 6, 2024):

This has the second most upvotes outside of Plaid integration. When perusing other feature requests with less votes, there are tasks done. Is it possible to get an update and some clarification on this? Thank you.

Unfortunately, the up votes never seem to mean anything, feature requests are done on a contributor basis based on what someone fancies doing, the core team rarely looks at the top voted features and implements them.

Dark mode for example got implemented because someone knew how to do it and wanted it not because it had lots of votes.
Transaction lock was implemented because a fork of Actual implemented that and pushed the changes upstream, again not because it had a lot of votes.

Have a read of this https://actualbudget.org/docs/contributing/leadership/new-core-contributors-guide "We do not assign specific roles or responsibilities but instead allow people to choose what they want to work on."

@rich-howell commented on GitHub (Apr 6, 2024): > This has the second most upvotes outside of Plaid integration. When perusing other feature requests with less votes, there are tasks done. Is it possible to get an update and some clarification on this? Thank you. Unfortunately, the up votes never seem to mean anything, feature requests are done on a contributor basis based on what someone fancies doing, the core team rarely looks at the top voted features and implements them. - Dark mode for example got implemented because someone knew how to do it and wanted it not because it had lots of votes. - Transaction lock was implemented because a fork of Actual implemented that and pushed the changes upstream, again not because it had a lot of votes. Have a read of this https://actualbudget.org/docs/contributing/leadership/new-core-contributors-guide "We do not assign specific roles or responsibilities but instead allow people to choose what they want to work on."

GiteaMirror commented

2026-04-26 01:18:41 -05:00

@Kidglove57 commented on GitHub (Apr 6, 2024):

Unfortunately, the up votes never seem to mean anything, feature requests are done on a contributor basis based on what someone fancies doing, the core team rarely looks at the top voted features and implements them.

Like you, I’m not clear as to what (or whether) there is a process for looking at up votes but I guess the hard reality is the volunteer developers will only work on those things that really appeal to their particular use case. Regrettably, I’m not clear how in an open source, volunteer led, project it can really be much different.

@Kidglove57 commented on GitHub (Apr 6, 2024): > Unfortunately, the up votes never seem to mean anything, feature requests are done on a contributor basis based on what someone fancies doing, the core team rarely looks at the top voted features and implements them. Like you, I’m not clear as to what (or whether) there is a process for looking at up votes but I guess the hard reality is the volunteer developers will only work on those things that really appeal to their particular use case. Regrettably, I’m not clear how in an open source, volunteer led, project it can really be much different.

GiteaMirror commented

2026-04-26 01:18:42 -05:00

@rich-howell commented on GitHub (Apr 7, 2024):

Unfortunately, the up votes never seem to mean anything, feature requests are done on a contributor basis based on what someone fancies doing, the core team rarely looks at the top voted features and implements them.

Like you, I’m not clear as to what (or whether) there is a process for looking at up votes but I guess the hard reality is the volunteer developers will only work on those things that really appeal to their particular use case. Regrettably, I’m not clear how in an open source, volunteer led, project it can really be much different.

What is the point in the votes then?

You could still have a team of volunteer developers who volunteer their time to work on Actual, tasks could be assigned to that team but that isn't how it works, however some aspects of the project are structured in a way that makes it seem like that is how it works.

I volunteer at a local railway, I don't get to just turn up and do what I want, the railway has a plan and I have to do what I am told, I couldn't just draw a pretty picture of a train in a different colour walk around the yard and get 100 signature's and then paint the train like my picture.

@rich-howell commented on GitHub (Apr 7, 2024): > > Unfortunately, the up votes never seem to mean anything, feature requests are done on a contributor basis based on what someone fancies doing, the core team rarely looks at the top voted features and implements them. > > > > Like you, I’m not clear as to what (or whether) there is a process for looking at up votes but I guess the hard reality is the volunteer developers will only work on those things that really appeal to their particular use case. Regrettably, I’m not clear how in an open source, volunteer led, project it can really be much different. What is the point in the votes then? You could still have a team of volunteer developers who volunteer their time to work on Actual, tasks could be assigned to that team but that isn't how it works, however some aspects of the project are structured in a way that makes it seem like that is how it works. I volunteer at a local railway, I don't get to just turn up and do what I want, the railway has a plan and I have to do what I am told, I couldn't just draw a pretty picture of a train in a different colour walk around the yard and get 100 signature's and then paint the train like my picture.

GiteaMirror commented

2026-04-26 01:18:43 -05:00

@ElDubsNZ commented on GitHub (Jul 9, 2024):

If we can get multiple accounts, it'd be great if we could also jointly control accounts.

i.e. I'd love if my wife and I could have our own accounts, but on top of that, if our shared account were added, it could show up on both our accounts, and sync with each other. It would make budgeting shared spending way easier.

@ElDubsNZ commented on GitHub (Jul 9, 2024): If we can get multiple accounts, it'd be great if we could also jointly control accounts. i.e. I'd love if my wife and I could have our own accounts, but on top of that, if our shared account were added, it could show up on both our accounts, and sync with each other. It would make budgeting shared spending way easier.

GiteaMirror commented

2026-04-26 01:18:43 -05:00

@dimaj commented on GitHub (Aug 5, 2024):

not quite what you are asking, but, if you are running ActualBudget as a docker container, nothing is stopping you from running multiple instances (on different ports) and assigning an instance to a family member/friend/partner.
You can even put it behind some sort of a reverse proxy (e.g. nginx or traefik) and assign each instance a sub-path.
This way, you'll be able to have something like:

Again, not a perfect solution, but it should do the trick fro the time being.

Edit:
I don't think Actual supports subpaths... so, you'll need to have subdomains for each instances:

@dimaj commented on GitHub (Aug 5, 2024): not quite what you are asking, but, if you are running ActualBudget as a docker container, nothing is stopping you from running multiple instances (on different ports) and assigning an instance to a family member/friend/partner. You can even put it behind some sort of a reverse proxy (e.g. nginx or traefik) and assign each instance a sub-path. This way, you'll be able to have something like: * https://actual.mydomain.com/joe * https://actual.mydomain.com/jane Again, not a perfect solution, but it should do the trick fro the time being. Edit: I don't think Actual supports subpaths... so, you'll need to have subdomains for each instances: * https://joe.actual.mydomain.com (or https://joe-actual.mydomain.com) * https://jane.actual.mydomain.com (or https://jane-actual.mydomain.com)

GiteaMirror commented

2026-04-26 01:18:45 -05:00

@urjeetpatel commented on GitHub (Sep 3, 2024):

One more item that user management should ideally add is to allow user accounts to be disabled. This way external authentication / sso at the reverse proxy level can be used. I.e. Forward auth using Traefik etc.

Would it be possible to add this to the user support wishlist.

@urjeetpatel commented on GitHub (Sep 3, 2024): One more item that user management should ideally add is to allow user accounts to be disabled. This way external authentication / sso at the reverse proxy level can be used. I.e. Forward auth using Traefik etc. Would it be possible to add this to the user support wishlist.

GiteaMirror commented

2026-04-26 01:18:45 -05:00

@o-mintaka commented on GitHub (Sep 10, 2024):

I was looking if there's any option to give read-only access to a budget. This feature request seems to be a good fit for that, wdyt?

In my particular case, my wife wants to have access and check our budget status but she isn't very comfortable with all the edit options that are possible (she is a mobile user and it annoys her that when she's looking around, she misclicks and opens edit boxes). I can also imagine that this would be a nice feature for other cases, like sharing budgets with your kids.

And alternative option could be to use a kind of public key for the budget, where it's possible to read data but all write/edit options are not possible and disabled.

@o-mintaka commented on GitHub (Sep 10, 2024): I was looking if there's any option to give read-only access to a budget. This feature request seems to be a good fit for that, wdyt? In my particular case, my wife wants to have access and check our budget status but she isn't very comfortable with all the edit options that are possible (she is a mobile user and it annoys her that when she's looking around, she misclicks and opens edit boxes). I can also imagine that this would be a nice feature for other cases, like sharing budgets with your kids. And alternative option could be to use a kind of public key for the budget, where it's possible to read data but all write/edit options are not possible and disabled.

GiteaMirror commented

2026-04-26 01:18:46 -05:00

@youngcw commented on GitHub (Dec 24, 2024):

🎉 initial support for multi user and OIDC was added in #3878 and will be available starting in v25.1 🎉

@youngcw commented on GitHub (Dec 24, 2024): 🎉 initial support for multi user and OIDC was added in #3878 and will be available starting in v25.1 🎉

Sign in to join this conversation.

Branches Tags

master

claude/hide-default-categories-1cwBZ

matiss/crdt-source-loading

youngcw/unlock-duplicates

matiss/crdt-protobuf

release/26.5.0

claude/update-issue-template-ykMNn

claude/fix-issue-7667-DPXi3

cursor/formula-feedback-improvements-4223

cursor/resolve-pr-7449-ee11

claude/fix-typescript-build-error-JPtZ5

jfdoming/api-tokens-part-3

jfdoming/api-tokens-part-2

jfdoming/api-tokens-part-1

claude/speed-up-vrt-workflow-ZAyI5

claude/crdt-version-auto-publish-Ph1BH

copilot/add-repository-configs-to-packages

worktree-compressed-drifting-ritchie

worktree-mellow-strolling-dawn

matiss/browser-api

claude/api-consumer-verification-kfz1K

feature/enable-banking

cursor/transaction-table-rewrite-f077

pr-7454

claude/fix-issue-7410-LLLQ4

release/v100.0.0

revert-7350-trim-deps

revert-7220-sankey-report

revert-7242-fix/split-parent-update-corruption

revert-7281-generate-icons

claude/electron-to-tauri-migration-LjBN8

worktree-remotion

release/vv26.4.0-pre

claude/browser-compatible-api-QbhHh

claude/improve-cli-transactions-waTUY

claude/publish-react-native-ios-j8qoT

js-proxy

claude/fix-flaky-ci-job-5gDdz

react-query-rules

react-query-useSchedules

claude/nightly-theme-validation-scan-DzOGD

claude/debug-simplefin-error-ZuKzB

matiss/desktop-client-subpath-imports

claude/fix-simplefin-ssrf-T31gX

claude/release-notes-validation-X7rvR

add-claude-github-actions-1772738270730

cursor/sync-performance-notification-9899

react-query-prefs

matiss/chunked-sync-and-progress-ux

v26.2.1

copilot/sub-pr-6880

fix-react-query-clear-on-close-budget

copilot/sub-pr-6140

feat/auto-note

feat/scoped-bank-sync

cursor/desktop-transactions-react-table-1d0c

fix-exhaustive-deps-App

copilot/fix-find-replace-bug

release/v26.2.0-pre

matiss/browser-tests

mobile-fix-drag-and-drop-across-groups

budget-table-v2

PayeeAutocomplete2

pglite

bugfix/plugins/fix-plugins-sw

feat/plugins/plugins-core-package

prerelease

matiss/unicode-minus-fix

cursor/fix-actual-github-issue-6206-gemini-3-pro-preview-9c37

TransactionFormPage

cursor/implement-mortgage-and-loan-account-type-78ca

tests-update-fill-with-pressSequentially

mobile/link-modal

deps/25.11

cursor/fix-update-vrt-apply-ci-job-dispatch-b324

sync-server-plugins

cursor/propose-patch-for-github-issue-5680-2a18

fix/compiler-preserve-inner-dollar-escapes

cursor/analyze-actual-budget-issue-and-propose-fix-5b70

coderabbitai/docstrings/0c070e5

cursor/add-wip-prefix-and-comment-to-prs-d78d

jfdoming/08-21-auto-focus-on-navigate-in-all-browsers

show-totals-on-mobile-budget-banners

allow-child-transactions-make-transfer

mobile-calculator-keyboard

payee-geolocation

enhance/restore_scroll_position

dm-fix-second-click-on-mobile-new-transaction-2

scrollToLocationBudget

alert-autofix-38

tsconfig-composite

mobile-fix-uncategorized-transactions-on-tracking-budgets

server-budget-handlers

fix-sql-injection-in-cleanup-template

non-chrome-draggable-workaround

mobile-budget-page-swipe-navigation

ts-db-all

stable

dark-theme-with-brand-colors

fix-mobile-delete-group

ts-db-select

UnderKoen/reconcile-context-menu

master-before-server-merge

v25.2.1

ts-runQuery

rename-redux-hooks

UnderKoen/3557-persist-state-in-history

remove-redux-CLOSE_BUDGET

fix-exhaustive-deps-errors-FinancesApp

redux-toolkit-createSlice-backup

accounts-function-component

ts-useSplitsExpanded

loot-core-server-package

useTransactios-in-TransactionEdit

react-aria-input

move-redux-to-desktop-client

QueryState-type

fix-themes-applied-late

mobile-vrts

revert-3295-spendingCardFix

react-aria-button-4

split-payee-on-mobile

twk3/pin-apis-crdt

notes-tag-autocomplete

ts-LoadBackup

dnd-kit

package-upgrades

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#41856