Permit — Roles, Permissions & Access Matrix

Permit — Roles, Permissions & Access Matrix — a premium, 100% offline digital tool by Aceplore. Runs entirely in your browser: no accounts, no subscriptions, your data never leaves your device.

A private, offline desk for access control — the full role and resource matrix, what inheritance really resolves to, and the one rule that decided each cell. 34 tools in one, and every resolution is traceable rather than merely stated.

34 built-in tools in one app. A grid of roles against resource-and-action showing allow, deny or blank; role, resource and action registers with destructive actions marked and resource sensitivity from public to regulated; a raw grant list and an EFFECTIVE view giving the resolved set after inheritance and denies; an inheritance graph with chain depth, a RESOLUTION view tracing one cell through every rule that touched it and NAMING the winner, a conflicts view where an allow and a deny meet, and a CYCLES view detecting inheritance loops and reporting them rather than recursing; coverage as cells and as a percentage — 196 of 336 is 58.333333%, and the counts are shown because a percentage over a small matrix means nothing; an over-broad view against a threshold you set, a least-privilege view, a DESTRUCTIVE view of who may delete, grants against sensitivity with restricted and regulated separated, and a SEGREGATION view listing every role holding a pair that should not be held together, treating an unrecorded need as unknown rather than as justification; users and their roles, a user-effective view giving the UNION across their roles with the contributing role named for each grant, orphans, LEAVERS still holding grants, and an escalation view of roles that can grant roles — the quiet route to everything; access review cycles with a coverage check, and a role comparison cell by cell; plus CSV exports, a JSON backup and a Method page.

Cells. 7 roles × 12 resources × 4 actions is 336 cells; 196 granted is 58.333333%.

Effective. Why a person can do something, and which role gave it to them.

What's included:

• Permit.html
• Quick-Start-Guide.html
• How-To-Use-Guide.html
• README.txt
• LICENSE.txt

Includes a personalized welcome wizard, an interactive guided tour, a ⌘K command palette, light/dark themes with 8 accents, and one-click JSON backup & restore.

Permit is a planning, costing and record-keeping tool for software and infrastructure work. Every figure it reports is computed by a stated formula from the numbers YOU enter, and every figure carries its UNIT, because a millisecond, a byte, a request, a vCPU-hour and a user-minute are different quantities and confusing them is the classic failure in this field. Byte and month conventions are settings and are printed beside the figures they produced — 1 KB = 1,000 bytes and 1 KiB = 1,024 bytes are both correct and they disagree. Where something is consumed against an allowance, the consumed amount, the remaining amount floored at zero and the overage are reported separately, because a negative remaining renders as headroom and that is how an outage gets missed. Where a figure rests on an assumption — a hit ratio, a growth rate, a base event rate, an hourly price — it is labelled an assumption at the point of use and is yours to change. It runs entirely in your browser with no network access of any kind: it cannot reach a server, a registry or a cloud account, and it reports only what you recorded. It does not predict an outcome and is not a guarantee of uptime, of a deploy, of a bill, of compliance or of security posture, and nothing in it is legal advice.