How to Build a Copyright Notice
A worked walkthrough of the actual fields, and what the generated declaration text looks like for a derived work versus original content.
- Contributor Name — how you're credited.
- License — locked to OGL 1.0a for PF1e content on this site; you never have to pick it yourself.
- Derived From — the specific source name and book, or left blank if the content is original.
- Referenced Product Identity — protected names your content references — yours or a third party's — that aren't part of the Open Game Content you're releasing. A disclosure, not a claim the site records; contributor-owned PI designation is a separate feature that isn't built yet.
"Derived from the Grizzly Bear (Pathfinder RPG Bestiary), used as Open Game Content under the OGL-1.0a. The game-mechanics content of this derivative work is designated as Open Game Content, contributed by [Contributor Name]. Product Identity of the original publisher is reserved by its owner and is not claimed here."
Original content generates a shorter declaration identifying it as such rather than crediting a specific source — there's nothing to cite when nothing was derived.
Every content type's edit page in the Forge carries this staged-attestation UI. The Publish button on that page previews the exact declaration text before it's written anywhere — nothing is generated silently, and the preview text is the literal text that gets permanently snapshotted once you confirm. That confirmation step also asks you to affirm a few plain-language representations (the content is Open Game Content you can publish; you own or have permission for it; any Product Identity is disclosed, not claimed) and records which ones you accepted alongside the declaration.
This is a real, live tool, not a hypothetical — any already-published record's own detail page shows its own generated Attribution card, built the same way.
Reviewed by Eco, 2026-08-26. Source: this site's own `render_ogl_declaration` publish-time renderer.