Overview
Use FileVault as the File Storage provider for the implemented files.upload.simple, files.bind and files.deliveryToken operations used by HomeBridge documents, document versions, payment-proof attachments and customer-visible delivery.
Capabilities
-
Upload files through files.upload.simple
-
Bind stored files to HomeBridge records through files.bind
-
Request secure delivery tokens through files.deliveryToken
-
Keep document categories, types, metadata, versions, links, access logs, and history in HomeBridge while storing file content with the provider
-
Retry failed FileVault operations through the declared filevault-retry worker
Setup Steps (6)
-
1
-
2
-
3
-
4
-
5
-
6
Step 6
Verify the record binding and secure delivery path, then confirm retry state is available for transient provider failures.
Limitations
-
File operations require an active File Storage provider binding and authorization.
-
HomeBridge record visibility rules remain part of document and property-workflow authorization.
-
Failed provider operations can remain queued until the retry worker processes them successfully.
FAQs
What document state does HomeBridge own?
HomeBridge owns document categories, types, metadata, versions, record links, access logs, history and provider references; FileVault supplies upload, binding and delivery-token operations.
Which FileVault operations are required?
Simple upload, record binding, and delivery-token generation.
How are transient file-provider failures handled?
HomeBridge records retry work and the filevault-retry worker processes pending operations every ten minutes.
Pricing
Starter
USD 365.17 / annual
Growth
USD 1,095.66 / annual
Enterprise
USD 2,921.89 / annual