SMB

Enable the SMB connector in your fastn dashboard, then let each customer authenticate their own SMB account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no SMB client code in your app and no per-customer branch in your codebase. Setup is 4 steps.

SMB is a specification rather than a service you sign up for, so there is no SMB account. Each customer supplies their own endpoint and credentials, and that connection is scoped to them, so they only ever reach their own files, documents and versions. The per-tenant isolation works the same way it does for a vendor product.

Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent lists a folder to locate the file it needs, then reads only that one.

fastn does. When SMB changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.

Each customer's own SMB grant. Where SMB holds a library, their existing folder and item permissions apply and your product cannot reach content the connected account could not reach itself. Where it processes content you supply rather than storing it, the call runs under that customer's own credentials and is logged per tenant.

Where SMB supports writes, documents, entries and assets can be created, updated and filed from your product or by an agent within scoped permissions, with each action logged. Where it is a read surface, the same connection serves reads only.

A common starting point: give each customer a way to nominate their own share and the paths they are willing to expose. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.

It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding SMB does not change your per-connector cost. You can start free with 3 connected accounts.