Single sign-on for clinical and administrative staff
Your team signs in to Foodzilla with the work account they already have. Google Workspace or Microsoft Entra ID, your own multi-factor rules, no second password to issue or reset.
Patients are different, and on purpose. Patient accounts are created inside Foodzilla with an email address and a password, so nobody has to put a patient in your staff directory.
Sign in to continue
What is single sign-on in Foodzilla?
Single sign-on lets your staff open Foodzilla with the same account they use for email and the rest of your systems. Foodzilla doesn't hold a password for them. It asks your identity provider whether the person is who they say they are, and your provider answers.
It covers the people who work for you: dietitians, clinicians, front desk staff, administrators, anyone with a Foodzilla login on your account. It is part of enterprise, and we set it up with your IT team rather than leaving you to work through a settings page on your own.
- Who it covers
- Clinical and administrative staff on your Foodzilla account.
- Which providers
- Google Workspace or Microsoft Entra ID.
- What patients use
- An email address and a password inside Foodzilla. No directory integration.
- Which plan
- Enterprise. Tell us on the enquiry form which provider you run.
How a staff sign-in works
Four steps, and three of them happen in systems you already control.
- 1A staff member opens your Foodzilla sign-in address.
- 2Foodzilla hands them to Google Workspace or Microsoft Entra ID.
- 3Your provider checks them, applying your multi-factor and Conditional Access rules.
- 4They land in Foodzilla with the role and permissions you gave them.
What you get
The point of SSO isn't convenience. It's that access lives in one place, and that place is yours.
One work account
Staff sign in with the Google or Microsoft account they already use every day. There is no Foodzilla password to issue, rotate or reset.
Your security rules apply
Whatever your provider enforces carries through to Foodzilla, including multi-factor and Conditional Access. We don't run a competing set of rules on our side.
Leavers lose access
Disable someone in your directory and their access to Foodzilla ends. If you need somebody out immediately, we can revoke a live session straight away.
Sessions on your terms
Sessions last up to 12 hours by default. Shared clinic workstations usually want less than that, so ask us to shorten it for your account.
Your own sign-in address
Your team signs in at an address like yourclinic.foodzilla.io, carrying your branding. Staff can reach it from your Microsoft or Google app portal.
Fewer password tickets
Password resets are one of the most common jobs on a clinic help desk. SSO takes Foodzilla off that list.
Patients don't need a directory account
Patient and client accounts are created within Foodzilla using an email address and a password. They never enter your staff directory, so you aren't buying identity licences for people you are treating, and your IT team isn't administering thousands of accounts that exist to open a meal plan.
It also keeps the line clean. Directory access means staff access. If someone shows up in your directory, they work for you.
- Staff and clinicians sign in through your directory, with SSO.
- Patients and clients sign in with an email address and a password in Foodzilla.
- Patient accounts need no directory integration and no licence from you.
How we set it up
Most of the work is a conversation with your IT admin and a pilot group.
- 1Tell us which provider you run and the email domains your staff sign in with.
- 2Your admin approves the Foodzilla app once, in your Google or Microsoft admin console.
- 3We wire your sign-in address and branding to your account.
- 4A small group signs in and we check roles, permissions and session length before anyone else moves.
- 5The rest of the team switches over. Existing Foodzilla accounts keep their clients, plans and history.
For the person doing the security review
Foodzilla is a cloud service running on AWS. We don't install anything on your servers, and SSO doesn't change that. Enterprise accounts choose the hosting region for their data, and we can complete your security questionnaire, sign a BAA, and share our data-flow summary and sub-processor list.
If your organisation needs a HIPAA-restricted workspace, or your review turns up a requirement we haven't covered here, put it in the enquiry and we'll work through it with you rather than send you a brochure.
Read how we handle security and privacySingle sign-on questions
Related Features
Explore more tools built for nutrition professionals
Enterprise
Hosting region, client and staff limits, security documentation and integration work.
Learn moreEpic integration
A SMART on FHIR app that reads patient data from Epic into a meal plan.
Learn moreSecurity and privacy
How we store, encrypt and separate the data you put in Foodzilla.
Learn moreHIPAA compliance
A locked-down workspace for recipes and meal plans, with no patient data in it.
Learn moreSoftware for clinics
What Foodzilla looks like in a practice with more than one clinician.
Learn moreDeveloper API
Connect your own website, checkout or CRM straight to your Foodzilla account.
Learn moreSet up SSO for your team
Tell us whether you run Google Workspace or Microsoft Entra ID, roughly how many staff need access, and when you want them signed in by.