Product Update — Enterprise sign-in, an API, and a portal for your clients

Four things landed this week, and they point in the same direction: Fily should fit inside how your organization already works, instead of asking you to work around it.

Sign in with your company account

Fily now supports single sign-on through Microsoft Entra ID (Azure AD), Okta, or any identity provider that speaks standard OpenID Connect. Your team signs in with the same account they use for everything else — no separate Fily password to provision, rotate, or forget. When someone leaves and IT disables their account, their Fily access goes with it, automatically.

Setup is on your side and takes a few minutes: register Fily as an application in your identity provider, hand us three values, and your people can sign in. New team members can be provisioned on first sign-in, restricted to the email domains you approve.

Two-factor authentication your organization can require

Any user can add a 6-digit authenticator code to their sign-in from their account page — scan a QR code with Microsoft Authenticator, Google Authenticator, 1Password, or anything else that does TOTP. Recovery codes are issued once, for the day the phone goes missing.

The part worth noting: an administrator can require it for the whole organization. Not a suggestion in a security policy document — an actual gate. Users who have not enrolled are walked through setup on their next sign-in and cannot get in until they finish. Most tools leave two-factor as an individual opt-in and quietly hope for the best.

A public API, and webhooks that tell you when work is done

You can now submit a file, check its status, and download the result from your own systems. One call uploads and creates the job; your credit limits, permissions and configured pipelines apply exactly as they do in the dashboard. Keys are issued per organization, scoped, and revocable on the spot.

Better than polling: register a webhook and Fily posts to your endpoint when a job is created, finishes, fails, or a review is finalized. Every delivery is signed so you can verify it really came from us, retried with backoff if your endpoint is down, and parked in a visible log if it never succeeds. We would rather give you one well-documented door than a list of connectors that never quite covers the system you actually use.

A portal for your clients, with your brand on it

If you are an LSP, your clients want to send you work without emailing you files and waiting. Each organization can now invite its own clients to a branded portal where they submit documents, follow status, and download deliverables — under your name, not ours. Your clients see their own work and nothing else.

Smaller but real

• Credit usage now shows the actual per-job charge, straight from billing.
• Purchase pages spell out what is included, in a list you can read at a glance.
• The published pipeline documentation now matches, step by step, what the pipeline really runs.

If single sign-on or the API is what was keeping Fily out of your stack, that objection is gone. Your Account Manager can walk your IT team through either one.