Public ID
Uhpenry's public-facing identifiers (PIDs) used across users, projects, Snapgates, Snapcharges, Snapshots, and documents.
A Public ID (PID) is a short, stable, user-facing identifier that Uhpenry displays on every major entity (users, projects, documents, Snapgates, Snapcharges, Snapshots, etc.). PIDs are designed for reference and communication they are easy to copy from the UI, paste into support tickets, include in emails, or embed in links.
PIDs are not database primary keys. They purposely decouple what humans see from the platform's internal identifiers.
In one line: Public IDs are for humans; internal IDs are for machines.
Why Public IDs?
- Support & Reporting Users or developers can report issues by quoting a PID and (optionally) a URL. Support can resolve a PID to the exact internal record instantly.
- Safety by Design Public identifiers avoid leaking database structure, cardinality, or guessable sequences inherent in raw internal IDs.
- Stability PIDs are immutable and remain valid even if the internal storage model changes.
- Consistency The same PID appears everywhere the entity is referenced (UI headers, emails, audit views, receipts, Snapshots).
Note: This guide is living documentation. We welcome contributions and corrections via GitHub or support@uhpenry.com.
Gated Source
Explains the Gated Source concept and how it affects access to projects, licensing, monetization, enforcement, and developer integration.
Access Model
Deep dive into Uhpenry's access model for Projects how access is chosen, enforced, and audited. Covers decision points, flows, security, and developer patterns.