Fonts and their rights
A font’s licence says what it may be used for: shown in an editor, used by a server to lay out documents, embedded in the PDFs it makes. Paprika records these rights where the font is kept, and checks them at every render. It never takes a request’s word for them.
Where fonts come from
Section titled “Where fonts come from”| Fonts | Rights |
|---|---|
| Bundled with Paprika | Every right; shared by every tenant |
| A tenant’s font library | As asserted by whoever added the font, for their organisation |
| Uploaded with a template in the editor | As asserted by the designer who uploaded it |
| In a published template version | Those its fonts had when it was published, kept with it |
Every font but the bundled ones is the tenant’s own: no other tenant can see or use it.
Asserting rights
Section titled “Asserting rights”Whoever adds a font confirms that its licence allows the uses ticked, for their organisation: the editor asks the designer, and the API wants confirm: true. The rights can’t go beyond what the font file itself allows: a font marked as not embeddable can’t be given the right to be embedded. Each assertion is recorded with who made it and when, and written to the audit log as font.rights.asserted.
At every render
Section titled “At every render”Rights are checked as they are now: laying a document out needs the backend right, making a PDF needs embed too. So a right withdrawn from a library font stops its renders at once, with an error naming the font, rather than at the next publish. Publishing a version whose fonts may not be embedded succeeds with a font-not-embeddable warning, so the designer knows before anyone renders it.
For a self-hosted install
Section titled “For a self-hosted install”You are the one who knows your organisation’s font licences. Before adding a commercial font to the library, check that the licence covers server use and embedding in documents you send out: many desktop licences don’t. The audit log answers who asserted what, and when.