Choosing an M7 service
Choose the service that owns the resource and workflow your application needs. A workflow can use several services; retain each service's identifiers and access context when moving between steps.
Storage and documents
Use BigFS for versioned objects, buckets, vaults, remote objects and storage operations. Its bucket guide and object guide describe resource access, uploads, downloads and stored versions.
Use Document for conversion, inspection, sanitization
and extraction. Authenticated document operations require an accessible
bucket_id; follow its bucket selection,
conversion and
job lifecycle contracts. Configure and authorize
the document operation according to those guides, even when your wider workflow
also stores files in BigFS.
Content and payload exchange
Use Blog for publication content, taxonomy, media, domains, revisions and public reading. Publication membership and capabilities control protected operations. Workspace selection and publication routes provide the entry path; public reading serves published content to readers.
Use Dead Drop for encrypted, time-limited handoffs. Projects select the authorized container. Drop lifecycle explains reservation, activation, retrieval, expiration and deletion. Protect the retrieval key according to its authorization guide.
Messages and proof workflows
Use Mailbox to send an email within an authorized project and inspect its send log. Sending describes the fields, accepted transport result and retry considerations. Transport acceptance does not establish that the recipient received the message.
Use Post to prepare reusable message templates, delivery policies and notification or proof jobs. Its jobs and proof guides describe activation, verification and consumption. Public proof steps use the job's documented credentials; protected management steps use project access.
Relationships and permission catalogues
Use Relationship for scoped connections, resource memberships, enrollment requests and mailbox event receipts. Scope setup and enrollment distinguish graph records from pending requests. Your application decides how a relationship permits access to its resources.
Use Capability to load an owner-enabled published catalogue's actions, presets, roles and defaults. Discovery specifies the project and revision lookup. Definitions describe actions; the receiving service still authorizes the caller's requested action against the selected resource.