Tenant, community and app
Three identifiers that look interchangeable and are not.
Tenant
Your organisation on the FanBase platform. Set as tenant on the provider, sent as the xb-tenant header on every request, and what scopes all data to you.
Wrong value, everything 400s. Missing entirely, you get a different dataset with a 200. Environment has the detail.
Community
A space inside your tenant, identified by a slug. Quests, fans and rewards belong to a community.
Most partners have one and can treat it as fixed. A tenant running several, say a club with separate spaces per team, has one slug per space.
The slug is an identifier. It is not a URL path, not a provider name, and not part of the sign-in flow. Passing a community slug where a provider is expected is a common early error.
App
An identifier for a specific surface or environment within a community, set as appId. Your local development app, your staging deploy and your production site are usually three different appId values against the same community.
Fans
A fan is one identity across everything in your community. Sign in with Discord on your main site and with Google on a campaign microsite, same fan, one progress record, if both are the same community.
Which one goes where
| Setting | Value |
|---|---|
tenant prop | Your tenant host |
slug prop | Your community slug |
appId prop | This app or environment |
provider in sign-in | google, discord, twitter or twitch only |
The last row is the one that trips people up. provider is the identity provider. Nothing about your organisation goes in it.