amari opened issue nhcarrigan/hikari-desktop#198

amari
Mon, 09 Mar 2026 13:01:21 -0700

198#the default permissions may not be applied correctly like i have read checked but it still asks for permission#

Default Permissions Not Applied Correctly

Description

Hey there! 👋 Thanks so much for flagging this — it's exactly the kind of thing that can be frustrating when permissions should "just work."

We're noticing that the default permission settings aren't being applied as expected. Specifically, when a user has "read" permissions checked in the defaults, the system is still prompting them for permission instead of granting access automatically. This suggests there's a disconnect between what's configured and what's actually being enforced.

This one matters because users expect their default permissions to be respected without friction — it's the whole point of setting defaults in the first place! Let's get this sorted so the permission system works as intended.

What We Know

Default "read" permission is marked/checked in settings

System still prompts for permission when it shouldn't

Expected behavior: access should be granted silently based on defaults

Acceptance Criteria

✅ Verify that default permissions (read, write, etc.) are correctly retrieved from the user's profile/settings

✅ Confirm the permission check logic actually compares against these defaults before prompting

✅ Test that a user with default "read" permission can access resources without additional permission prompts

✅ Ensure the fix works across all permission types (read, write, admin, etc.)

✅ Add a test case that would catch this regression in the future

Next Steps

This will need someone to dig into the permission-checking logic and trace where the disconnect is happening. Could be in retrieval, comparison, or enforcement — we'll figure it out together!

Thanks for bringing this to our attention. 💙