Idea: a public-reference field in a custom CRM app

[PerchAnton]

I maintain RefMint, a TypeScript library for public references with a type prefix and a Bech32m checksum.

Use case

Twenty supports custom CRM objects and app extensions. A case-management app could expose a reference that a customer reads back while keeping the underlying object ID internal.

Proposal

Try RefMint in an optional custom app with a fixed case prefix and an authorized lookup. The experiment would use a separate field, avoiding changes to core object identifiers or migrations for existing records.

Trade-offs and current status

The first alpha is available as a GitHub package archive, not on npm. It targets Node 22+ and Web Crypto browsers, with no runtime dependencies. The format may change and adds six checksum characters. A checksum is not authorization. Keeping the current reference format is a valid alternative.

I checked the released package (generation, formatting, parsing and typo rejection); I have not tested an integration here or measured a benefit for your users. Would this optional workflow be useful, or is the current approach sufficient?