What problem does this solve in your TCC permission workflow?
The current export flow explains that a modified copy is downloaded, but it does not clearly call out that the exported file uses a _modified suffix. That can create confusion during the manual replace/copy step.
What behaviour do you want?
Update the footer / notice text to explicitly mention that exported files are saved with a _modified.db suffix.
Also clarify what the user should do next:
- if using terminal copy commands, they can copy the exported file directly to the target
TCC.db path
- if manually replacing/renaming files in Finder, they may need to rename the file back to
TCC.db first
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This is a small but important UX clarification in the local file workflow that Clearance already supports.
Scope check
Please confirm this request fits the project scope in CONTRIBUTING.md: local file workflow, no network dependency, and no writes to system TCC files.
Additional context
The app already exports with _modified.db; this issue is specifically about making that behavior more obvious in the UI near the export/apply action.
What problem does this solve in your TCC permission workflow?
The current export flow explains that a modified copy is downloaded, but it does not clearly call out that the exported file uses a
_modifiedsuffix. That can create confusion during the manual replace/copy step.What behaviour do you want?
Update the footer / notice text to explicitly mention that exported files are saved with a
_modified.dbsuffix.Also clarify what the user should do next:
TCC.dbpathTCC.dbfirstWhy does this fit a local macOS TCC editor instead of a system tool or third-party service?
This is a small but important UX clarification in the local file workflow that Clearance already supports.
Scope check
Please confirm this request fits the project scope in
CONTRIBUTING.md: local file workflow, no network dependency, and no writes to system TCC files.Additional context
The app already exports with
_modified.db; this issue is specifically about making that behavior more obvious in the UI near the export/apply action.