# Multiple credentials, more query power and more powerful attributes

**URL:** <https://community.silverbullet.md/t/multiple-credentials-more-query-power-and-more-powerful-attributes/3143>\
**Category:** Ideas\
**Created:** [September 4, 2025, 8:59pm UTC](https://community.silverbullet.md/t/multiple-credentials-more-query-power-and-more-powerful-attributes/3143 "2025-09-04T20:59:10Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![MrMugame](https://community.silverbullet.md/user_avatar/community.silverbullet.md/mrmugame/32/358_2.png) [@MrMugame](https://community.silverbullet.md/u/MrMugame)\
**Post date:** [September 4, 2025, 9:45pm UTC](https://community.silverbullet.md/t/multiple-credentials-more-query-power-and-more-powerful-attributes/3143/2 "2025-09-04T21:45:37Z")

</div>

1. You could just have one general user and then use a little bit of space lua with the `clientStore` to save the user. Selecting the user could be done by prompting the user if no user is yet saved with `editor.filterBox`, similar to the index page “hack”, just with a prompt instead of a navigation. Multi user setups aren’t really a goal of SB to my knowledge and the same applies to an extensive authentication system.
2. This would be very performance heavy currently. Although possible to add.
3. ~
4. This is in fact quite true, as `{sub1:val1,sub2:val2}` is just not doing the thing in YAML you think it should do, SB is working correctly here. You probably want to use `{sub1: val1,sub2: val2}`
5. What would be your usecase? What speaks against using widgets?

About the lua engine, [there are good reasons for that](https://community.silverbullet.md/t/space-lua-making-space-script-safer-simpler-and-unifying-all-the-things/970)

---

_[View the full topic](https://community.silverbullet.md/t/multiple-credentials-more-query-power-and-more-powerful-attributes/3143)._