macOS controls what an application may open. Balise remembers the permissions you grant, but some stop working.
I denied access to Documents or Desktop
What happens. macOS remembers the denial and may not show its confirmation again when Balise retries. The other location remains independent: denying Desktop does not remove Documents access.
What to do. Open Settings > Permissions, select Documents or Desktop, then choose System Settings…. In Privacy & Security > Files and Folders, allow Balise. Return to Balise and choose Check Again.
You can also leave access denied. Files elsewhere and files explicitly handed to Balise by macOS remain usable.
A favorite or workspace no longer opens
What happens. macOS no longer honors the permission for this target. Usually the file or its parent folder has moved, been renamed or is on an unmounted volume.
Your data is not affected. The file is where you left it.
What to do. Open Settings > Permissions. For a folder, click Manage Folder Access…; for a file, expand Saved file access. Find the row marked Needs renewal, then click Renew. Choose the same target in the panel that opens.
If you no longer know which file it is, Reveal shows it in Finder.
Balise asks permission for a file I already authorized
What happens. Permission applies to the target as it was when you selected it. Moving, renaming or restoring it from a backup creates a new target from macOS’s perspective.
Your data is not affected.
What to do. Grant access again, then remove the obsolete row with Forget.
I clicked Forget by mistake
What happens. Balise removed its saved access reference for this target. This does not revoke permissions granted in macOS.
Nothing was deleted. Forgetting does not touch the file, folder or their contents. A window already open on it retains access until closed.
What to do. Reopen the target through File > Open…, then add it to favorites again.
A permissions row has neither Renew nor Forget
What happens. Documents, Desktop, Downloads and some capabilities such as networking are managed by macOS rather than revoked by Balise.
What to do. For Documents, Desktop and Downloads, use System Settings…, then Check Again in Balise.
A file dropped onto Kanban was not copied
What happens. The file came from a location Balise cannot read, and macOS blocked reading.
Your data is not affected.
What to do. Balise explicitly asks permission before copying: accept the request. If you denied it, drop the file again.