Editions from your own systems, published by a person.
When an edition comes from something you run, like a generated digest, a daily puzzle or a report your team builds, BlastsFlow can accept it through a signed connection. It waits in your review queue until someone on your team publishes it.
- Your system
- Signed ingest
- Review queue
- A person publishes
- Readers
Registered by BlastsHub staff
Each producing system is registered for your organization by BlastsHub staff, who issue its signing secret once. There is no self-serve registration and no open inbox.
Signed and deduplicated
Every item is signed with its producer's own secret and checked before it is accepted. Each item carries the producer's own id, so a retry is recognized instead of creating a duplicate.
Held for review
Items land in your Hub's review queue, visible to owners and administrators, shown exactly as readers would receive them and with the audience they go to.
Published by a person, sent now
Publish sends the item immediately to its audience, by email and on Blasts. Approve only records a decision and sends nothing. The queue does not schedule: a time a producer asks for is not acted on.
The source stays attached
Every item keeps its producing system and its status from review to publication, so you always know where an edition came from.
Nothing filed this way is sent until a person presses Publish.
Start with your publications.
Set up your publications and readers first. When you have a system that should file editions, ask BlastsHub staff to register it.