What problem does this solve in your TCC permission workflow?
The permission table currently presents the same set of service columns for every app, which can imply that every permission is equally relevant for every entry. In practice, many apps will never request certain services, so editable cells for those permissions create noise and can be misleading.
What behaviour do you want?
For each app row, disable or grey out permission cells that are not relevant to that app. For example, if a text editor has no evidence of requesting Camera access, the Camera cell should appear disabled rather than editable.
The decision could be based on a combination of:
- existing TCC rows/history in the loaded database
- local app metadata where available
- a conservative fallback that avoids over-hiding cells when confidence is low
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This is a local UX improvement that helps users understand which permissions matter for each app while staying entirely inside the existing TCC audit/edit workflow.
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
It may be helpful to add a tooltip or legend for disabled cells, for example: “No evidence this app requests Camera access.” That keeps the UI informative without implying certainty the app can never request that permission.
What problem does this solve in your TCC permission workflow?
The permission table currently presents the same set of service columns for every app, which can imply that every permission is equally relevant for every entry. In practice, many apps will never request certain services, so editable cells for those permissions create noise and can be misleading.
What behaviour do you want?
For each app row, disable or grey out permission cells that are not relevant to that app. For example, if a text editor has no evidence of requesting Camera access, the Camera cell should appear disabled rather than editable.
The decision could be based on a combination of:
Why does this fit a local macOS TCC editor instead of a system tool or third-party service?
This is a local UX improvement that helps users understand which permissions matter for each app while staying entirely inside the existing TCC audit/edit workflow.
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
It may be helpful to add a tooltip or legend for disabled cells, for example: “No evidence this app requests Camera access.” That keeps the UI informative without implying certainty the app can never request that permission.