Enterprise
Fanzava for large employers.
The questions your IT, procurement and HR teams ask first, answered plainly. Where something is built but not yet proven with a customer, or is still on our roadmap, we say so.
Security and compliance.
Controls in place, certification on our roadmap. Our security page has the detail to forward to your IT team.
- Certification status.
- We run controls aligned to the SOC 2 security, availability and confidentiality criteria. We hold no SOC 2 or ISO 27001 certification today and have not completed an audit. Our infrastructure providers hold certifications of their own, and those belong to them.
- Every hub is its own tenant.
- Your participants, scores and settings are separated from every other hub's data at the database, not just in the interface.
- Privacy requests.
- Members can ask for access to their data, an export, or deletion. Hub admins can export hub data.
- Procurement support.
- Included on Enterprise. Tell us what your security review needs and we will say what we can provide.
Sign-in and SSO.
Single sign-on is an Enterprise feature, so your staff sign in through your own identity provider.
- SAML 2.0 and OpenID Connect.
- Built on both standards and set up by your hub admin, with signed-assertion verification and an allowed email domain list. It has not yet been run against a customer's identity provider, so raise yours with us before you commit.
- SCIM 2.0 provisioning.
- Available to Enterprise customers and set up with our team. It is not a self-serve setting.
- What your identity team will see.
- The connection details carry Fanzava's platform name, not yours.
- Admins need two-factor.
- Hub admins must enrol an authenticator app before they can change anything, on every plan. A hub can also require it of every member. Authenticator apps are the only method today.
Data residency.
Hubs run in regional cells. Australia (Sydney) and the EU (Frankfurt) are live. A US cell is built and is not serving hubs yet.
- Choosing a region.
- Enterprise customers choose their region. Every other hub is placed by location at sign-up. Moving a hub later is an assisted migration, not a setting.
- What follows the cell.
- A hub's database rows live in its cell, and its email is sent from the matching mail region. UK and France are email regions, not data cells, and are served from Australia.
- What we do not promise.
- We do not say that nothing ever leaves a region. Routing indexes and some stored files are not tied to a zone. Ask us for the detail your review needs.
Admin controls and roles.
Run it with the people you already have, and keep a record of who changed what.
- Roles.
- Hub admins, moderators and members. Add as many hub admins as you need. Group moderators review and approve or reject flagged banter in their own group.
- Groups.
- Organise people into groups for departments, offices or regions. Group limits grow with the plan and are unlimited on Enterprise.
- Getting people in.
- Share an invite link, invite by email, or upload a CSV of up to 5,000 emails at a time. Each person gets an invitation and joins when they accept. Group invite links come with a QR code.
- Audit log.
- Kept for 12 months on paid plans and 2 years on Enterprise, configurable up to 7 years. A hub admin can export it as JSON or CSV through the API.
Seats and invoicing.
There is no hard ceiling on how many people can play.
- Seats above 1,000.
- Scale covers 1,000 participants and capacity can be added in blocks of 50 beyond that. Enterprise has no participant limit.
- Invoiced billing.
- Enterprise customers can pay by invoice on 14 or 30 day terms, arranged with our team. It is not a self-serve setting.
- Plans and prices.
- Every self-serve plan, with its price and participant limit, is on the pricing page.
Your domain and your branding.
Your logo, colours and name in front of staff, and your own address when you are ready for it.
- Fanzava branding.
- The Fanzava watermark comes off from Starter. The Free plan keeps a “Powered by Fanzava” mark.
- Your own domain.
- A custom domain and email sent from your own domain start on Pro. Your hub admin sets the domain up themselves; some apex domains are reviewed by our team first.
- Before that.
- A hub sits at a fanzava.com address and sends from a Fanzava email domain, and social sign-in screens carry Fanzava's name.
Support.
Email support on paid plans, with priority queues from Pro.
- A named account manager.
- Enterprise includes one person who knows your hub, your audience and your renewal date.
- What we do not publish.
- We do not quote an uptime percentage or a contractual response time on this page. Ask us what your contract would cover.
Talk to our team about your rollout.
Tell us your headcount, your identity provider and where your data has to sit. We will say what fits today and what does not.