Problem
What made this hard
Clients needed faster access, but a public link would weaken accountability. The experience had to balance convenience with permission scope, expiry, revocation, and traceability.
All case studies09 / 11
Reporting · Security experience · 2026
Secure Permalinks
Share a report quickly without giving up control.
RoleProduct DesignerStatusIndependent conceptContextTapClicks · Client reportingEvidenceSecurity experience · Permission model · Visual concept
Outcome
What changed
A governed sharing model where administrators set boundaries before creating a link, then review or revoke every active share from one place.
The thesis
A concept for agency administrators to share familiar dashboards through controlled links with clear ownership, scope, expiry, and audit history.
Case-study proof
The decision record
Enough context to judge the choice, inspect the work, and separate evidence from ambition.
Why this, not that
I treated each share link as a governed object instead of an anonymous public URL. The extra setup step was intentional: ownership, view-only scope, expiry, recent access, and revocation had to remain inspectable.
Why this case is specific
The concept addresses agency administrators sharing TapClicks-style client dashboards, where faster access still has to coexist with permission scope and an audit trail.
What you can inspect
Independent concept · static interface modelThe page shows a create-link state and an active-share ledger. These are static concept screens, not a functioning permission system.
Decision to outcome
The model connects the decision to add governance with an auditable create-and-revoke flow. Security review, administrator comprehension, and telemetry remain required before any release claim.
Interface evidence
Remove access friction, keep accountability
Opening a report can be easy while the decision about who can see it remains deliberate.
Treat every link as a governed object
Each share has an owner, scope, expiry, and status rather than behaving like an anonymous address.
01 / Tension
Remove access friction, keep accountability
Opening a report can be easy while the decision about who can see it remains deliberate.
02 / Model
Treat every link as a governed object
Each share has an owner, scope, expiry, and status rather than behaving like an anonymous address.
- Explicit view only scope
- Optional expiry
- A name for audit clarity
- Revocation in one action
- Recent access visible
03 / Experience
Keep the client view familiar
Recipients see the reporting surface they already know. Administrative controls remain outside the client view, reducing confusion and accidental exposure.
04 / Next
Validate security and comprehension together
The model still needs security review, administrator testing, and telemetry for creation, access, expiry, and revocation before release.
Supporting evidence
Keep the client view familiar
Recipients see the reporting surface they already know. Administrative controls remain outside the client view, reducing confusion and accidental exposure.
Validate security and comprehension together
The model still needs security review, administrator testing, and telemetry for creation, access, expiry, and revocation before release.
Bring me the difficult part.
Complex workflows, AI trust, and enterprise systems.
Discuss a product challenge