Studios, namespaces, and titles
PlayFab organizes resources into studios, namespaces, and titles. Each scope has a different purpose.Studio
A studio is the administrative grouping you use in Game Manager. A studio contains your PlayFab titles and controls team membership, roles, permissions, billing, and support access. Studio membership and permissions don’t represent player identity or gameplay data.Namespace
A PlayFab namespace defines the cross-title player identity and shared-data scope for a studio. It allows PlayFab to recognize the same player across multiple titles and supports data that is shared by those titles. By default, a studio has one namespace and all titles in the studio belong to it. A title can belong to only one namespace and can’t be moved between namespaces. Some PlayFab APIs and Game Manager pages use the older term publisher. The Publisher ID identifies the namespace. In this context, publisher and namespace refer to the same cross-title scope; neither term means the studio itself.Title
A title is the PlayFab resource boundary for a game or game environment. Each title has its own Title ID, configuration, title-specific player accounts, data, secrets, and service settings. A studio can contain multiple titles. You might create separate titles for different games operated by the same business, or for different service environments that require isolated configuration and player data (dev/test/prod). Data stored at the title level isn’t automatically shared with other titles. Use namespace-scoped features when player identity or data must span titles. Namespaces and titles are also built-in entity types. Other built-in entity types represent scopes such as players, groups, and servers.Developer identity and Game Manager
To keep your game data secure, developer identity is used to authenticate users and manage administrative access to studios and titles. It’s easy to create a PlayFab account and sign in with your Microsoft account. Assign PlayFab user roles to grant access to other members of your development team. PlayFab’s web portal is called Game Manager and is the primary interface for managing your studio and title configuration. Most functionality in Game Manager also has a REST API equivalent, so you can script and automate configuration changes in the later stages of production.Title configuration
Once you have a title, you can start storing data to Title Data. This data has the broadest access policy, allowing all of your game clients and servers to view TitleData. General game configuration settings are often stored in TitleData, and it’s typical for game clients to read this data during initialization. The Title News features provide specific tools for title-wide communication with your players. Similarly, at the namespace level, Publisher data is accessible from any title tied to the namespace and can be useful for cross-game promotional events or news that might interest your entire player community. Publisher data uses the older API term for namespace-scoped data. Sometimes you want to set configuration data that targets a subset of your title’s players. For targeted configuration, use Segmentation to define players in a target segment. Experimentation is another option for testing different configurations on parts of your player base.Player identity
The PlayFab player identity system is responsible for verifying client details and issuing authorization tokens. We support most common third-party providers, such as XBOX, Steam, iOS, Android, Nintendo, and PlayStation™ Network. PlayFab clients must authenticate before accessing most PlayFab APIs. Beyond authentication, accounts also serve as the central pillar around which your game systems are built. Using a recoverable account makes it easy to save and retrieve player-specific data regardless of which platform or device the player is currently logged in with. Data such as permissions, player progression, player friend lists, or player bans are just some of the types of player-specific data that you might want to store for retrieval or sharing. A player has amaster_player_account in the namespace. When the player signs in to a title, PlayFab creates or uses a title_player_account for that title. The master player account provides cross-title identity, while each title player account contains title-specific identity and data.