quillDrop
Das Backend ist nicht erreichbar. Starten Sie es mit python3 server/server.py — der einfache statische Server kann niemanden authentifizieren.
workingFlow
Hallo Pam,
Das Verkaufsgespräch war ein voller Erfolg und das ganze Papier ist beim Kunden angekommen. Melden Sie sich bitte, falls Sie demnächst einen Anruf von deren Team erhalten.
Freundliche Grüsse,
Every signature is generated from this design — only the personal details are swapped per person.
| (e.g. FMH Allgemeine Innere Medizin | Ärztlicher Leiter).Import a client's existing signature in the Signature Editor and save it as a profile — then select it here as the template.
Die aktiven Mitarbeitenden werden unten wie eine CSV-Datei eingetragen. Beim Senden an Git wird jede Signatur mit dem Konto der Person verknüpft und in ihrer Abteilung abgelegt.
One person per line — columns separated by ; , or tabs. The name can be a single Full name column, or split into Academic title (e.g. Dr. med.), First name and Last name — put any second name in the first-name field (e.g. John Dilly · Doe). For several job-title lines (specialty, role…) separate them with | — e.g. FMH Kardiologie | Oberärztin. The image column is optional; columns are auto-matched after loading and can be remapped.
Match each column to a field. The name can be a single Full name column, or split into Academic title · First name · Last name.
Pick a template and add your CSV list above,
then hit Generate signatures.
| # | Person | Status |
|---|
Select a template on the left, or create a new one.
This is the library of finished templates — their name, company, department,
publish window and version history live here. The content itself is designed
in the Signature Editor: open a template with Edit in Signature
Editor, then bring your changes back with Update from editor.
Older versions of this template — Preview shows one in the preview pane below, Restore makes it current again (the replaced state is archived too).
Content is designed in the Signature Editor — use Edit in Signature Editor above, then Update from editor to bring it back. The fields this template fills in per person:
Select a signature on the left.
Finished, fully-resolved signatures — one per real person — live here,
separate from the editable {{placeholder}} Templates. Generate
them from the Signature Editor or the Bulk Generator (a "Push to Git" button
sits next to Copy/Download in both places), then push them here to this
customer's git repository. Need to tweak one? Use "Open in editor" to load it
into the Signature Editor, make your changes, then "Update from editor" to
save them back here — no download/upload round trip needed.
Nicht gespeicherte Änderungen im Signatur-Editor — klicken Sie auf «Aus Editor aktualisieren», um sie hier zu speichern.
Select a document on the left.
Each company gets exactly one signatures.json manifest, plus any
number of profile.json overlays — both documented in quillDrop's
CONFIG.md and read by the macOS app. Synced to this company's git
repository under config/.
| When | Who | Action | Target |
|---|
Select a company on the left, or create one.
A company groups employees and owns its signature templates —
every user assigned to it automatically gets the company's
templates as their signatures.
Select a user on the left, or add a new one.
A user account controls sign-in and holds the profile fields (name, title, contact
info, photo) their signatures are generated from — plus, for admins, their role
and company assignment.
Select a role on the left, or create one.
A role is a named bundle of permissions assigned to users.
The built-in system roles are locked; create custom roles to mix
permissions differently — e.g. an MSP trainee who may use the
editor but not the bulk generator.
One account can authenticate to many customer repositories over HTTPS.
Select a service account on the left, or create one.
A service account is a git host username + access token — attach it to a
company's repository below to push over HTTPS.
Each company gets its own git repository — set the remote, a short code, and (for an https:// remote) which service account authenticates to it.
Select a company on the left.
Keycloak proves who someone is. quillDrop still decides whether they may in and what they can do — deactivating an account here blocks it immediately, whatever the identity provider says.
Saved here, not in .env — those values only seed
a brand-new install. Changes take effect at once; no restart, and no shell
on the server.
Off, someone must exist here before they can sign in, and their permissions are quillDrop's alone. On, the realm decides both: create the person in Keycloak once and they get an account here on first sign-in, with the role their client roles map to.
Anyone carrying none of these roles is refused — no account is created and nothing is written. New accounts start with no company; assign one in Admin → Users, or they sign in to an empty app. They can never sign in with a password, whatever the setting above.
Who did what, newest first — logins, user and template changes, overrides, imports. The log keeps the most recent 5000 entries.
| When | Who | Action | Target | Detail |
|---|
Showing activity for your company only. Instance-wide actions, and anything logged before per-company activity tracking was added, are visible to administrators only.
Showing the latest 200 matches — refine your search to narrow further.
Wie oft in den letzten sieben Tagen nach Git gepusht wurde und wie oft das fehlgeschlagen ist. Zählt Vorgänge, nicht einzelne Signaturen — ein Massen-Push ist ein Vorgang.
| Tag | Vorgänge | Fehlgeschlagen |
|---|
Fehlschläge nach Firma
| Firma | Fehlgeschlagen |
|---|
Jeder Git-Vorgang mit Zeitpunkt, auslösender Person und verwendetem Git-Konto, dazu alles, was derzeit fehlschlägt. Der Verlauf beginnt mit der ersten protokollierten Zeile; die Fehlerliste zeigt immer den aktuellen Stand.
Fehlgeschlagen — Handlung erforderlich
| Firma | Ziel | Bereich | Letzter erfolgreicher Push | Fehler |
|---|
Letzte Vorgänge
| Wann | Firma | Wer | Aktion | Ziel | Konto / Detail |
|---|
Es wird nur die Git-Aktivität Ihrer Firma angezeigt.
Tip: pasting the rendered signature (Copy Signature) works in almost every client. The HTML code and .html file are for manual edits and automated rollout.
Tip: use Copy rather than Download — pasting the rendered signature works in almost every mail client. Download is for sending the file to your IT support.