Playground has two levels of settings: enterprise and location. If you manage more than one site, it’s important to understand the difference, since some changes affect every location while others only apply to the one you’re viewing.

If your organization has more than one location, your settings are split between two levels: enterprise and location. Both live in Playground, but they do different things.

Enterprise settings live on the Enterprise dashboard and are designed to support your organization as a whole. Some of these settings apply across every location automatically. Others establish defaults that locations can follow or adjust depending on how your account is structured.

Location settings live within each individual location. These control day to day operations for that specific site. Changes made here typically affect only the location you are actively viewing.

It’s also important to know that not every setting exists at both levels. Some controls are only available at the enterprise level and cannot be managed per location. Others are only available within a location and do not appear in the Enterprise dashboard at all. Understanding where a setting lives helps you decide where to make changes. If you want an update to apply everywhere, you may need to adjust it at the enterprise level. If you only want it to affect one specific site, you’ll likely manage it within that location’s settings.

In the sections below, we’ll walk through the major settings available at each level, where to find them, and how they impact your locations.
​

The General tab in the Enterprise dashboard includes most of the same settings you’re used to seeing at the location level, such as center details, timezone, and attendance preferences. If you are already familiar with the General tab at a single location, much of this will feel familiar.

However, there are important differences.

At the top of the Enterprise General tab, you’ll see a banner clearly stating that these are enterprise wide settings. Any changes made here will override center specific settings. This is your visual confirmation that you are working at the enterprise level, not inside an individual location.
​
​

Any updates made in this view will impact all of the sites

Immunization schedules are managed entirely at the enterprise level. From the Enterprise dashboard, you can enable immunization tracking and create multiple immunization schedules. Each schedule can then be assigned to specific locations. For example, if several sites follow one customized schedule and others follow the standard CDC schedule, you can configure that here.

It is completely possible to:

• Assign one customized schedule to a group of locations
​

• Keep other locations on the default CDC schedule
​
​

All schedule creation, editing, and assignment happens within the Enterprise General tab. If you navigate to Settings within an individual location, you will not see the option to manage immunization schedules there. That control only exists at the enterprise level.
​
​

For step by step instructions on creating and assigning immunization schedules, take a look at our article.
​

Billing at the enterprise level doesn’t behave the same way as the General tab.

In General, when you change something at the enterprise level, it typically applies across locations. Billing is different. Think of enterprise billing settings as a default setup, not a locked rule. There aren’t any additional billing features at the enterprise level. The settings themselves are the same ones you see within a location’s Billing tab. What’s different here is how those settings apply across locations.

Locations can still configure their own billing settings. If a location’s billing setup differs from what’s set at the enterprise level, the location’s configuration takes priority.

When that happens, you’ll see a small broken link indicator next to that billing setting showing that it isn’t aligned across all sites. It’s there to signal that at least one location is doing something different. If you hover over that icon, you’ll see exactly which locations are using a different setup. That way, you don’t have to click into each one to figure out where the variation is.
​

This flexibility is intentional. Billing structures often vary by site, whether because of state requirements, operational differences, or internal decisions. The enterprise billing tab gives you a baseline, while still allowing individual locations to run billing in the way that makes sense for them.

If something about billing feels inconsistent across your locations, this is usually the first place to look.

The Scheduling tab exists at both the enterprise and location levels. At the enterprise level, the settings you configure act as the default for all locations. This includes core scheduling logic such as overage billing rules, grace periods, overtime rates, and how full time equivalents are calculated. These are foundational rules, and as a best practice, they’re typically kept consistent across sites to maintain predictable scheduling and billing behavior.
​
​

However, locations can override these defaults in their own Scheduling tab. If a location updates its scheduling settings locally, those changes will apply only to that site. If you notice differences in scheduling behavior between sites, it’s likely that one or more locations have adjusted their settings directly within their own Scheduling tab. If something doesn’t match what’s configured at the enterprise level, the next step is to check the Scheduling tab within that specific location.

Scheduling settings follow each location’s assigned time zone, especially if the location has not adjusted its Scheduling settings locally. If you set overage billing to begin at 7:00 PM at the enterprise level and a location keeps those default settings in place, that means 7:00 PM local time for that site.

So if one location is in Eastern Time and another is in Central Time, the system automatically adjusts based on each site’s configured time zone. As long as the location hasn’t overridden the enterprise setting and its time zone is set correctly in General settings, scheduling will align with that local time.

The Custom values tab at the enterprise level gives you access to custom field categories and custom fields for students, guardians, and staff. From here, you can create new custom field categories, add custom fields, edit existing ones, and control which roles can see them. This works the same way you may be used to at a single location, but at the enterprise level you’re managing them across sites.
​
​

What you won’t see here are the Lessons, Notes, or Expense categories sections that appear in location settings. Those sections only exist at the location level. Any lesson units, lesson tags, note tags, or expense categories created there live within that specific location.
​
​

Even though those items are managed locally, enterprise level reports can still pull in that data when applicable.

Custom field categories and custom fields can be created either at the enterprise level or at an individual location. When creating or editing a custom field, you’ll choose which sites it’s assigned to. If it’s assigned to multiple locations or to all sites, it will appear in those locations’ settings automatically. You can then view and manage it from either the enterprise Custom values tab or from the assigned location’s settings.

The same logic applies in reverse. If a custom field is created at the location level and assigned to additional sites, it will also appear in the enterprise Custom values tab. As long as the field or category is assigned to that location, it will be visible in that location’s settings.
​
​

In short, custom fields and categories sync based on assignment. Lessons, notes, and expense categories do not.

The Roles tab is managed entirely at the enterprise level. There is no separate Roles tab inside individual location settings. All role creation and management happens here. This includes creating new roles, editing existing roles, and defining what each role can access across Playground.

The list of roles on this page applies across your entire organization. That includes roles used at individual centers as well as roles that are specific to enterprise level access. There isn’t a separate place to manage “center roles” versus “enterprise roles.” Everything lives together in this tab. If you’re creating a new role, whether it’s location based or enterprise based, that always happens here in the Roles tab. This is where you define permissions and build out the role itself.

From the Staff tab in the Enterprise dashboard, you can add a new enterprise staff member and assign them an existing enterprise role. You’ll choose from the list of enterprise roles that have already been created.
​
​

​
You cannot create a brand new role from the Staff tab. If a new role is needed, Enterprise or otherwise it must first be created here in the Roles tab before it can be assigned.When you create or update a role, those changes affect that role anywhere it’s assigned, regardless of location. Because of this, role updates are typically handled by enterprise administrators rather than individual sites.

If your organization did not originally start as an enterprise account and later transitioned into one, any roles that were previously created at the location level will automatically move to the Enterprise dashboard. Once your account becomes an enterprise, all roles are centralized at the enterprise level.

When you open the Feed tab in Enterprise Settings, you’re looking at the centralized configuration area for Feed post types across your organization. This Settings tab only exists at the enterprise level. You won’t see a Feed tab inside the Settings of an individual location.

That said, locations absolutely still use the Feed tool from their dashboard. Staff can post, view activity, and use any post types assigned to their site. What’s different here is that this is where post types are created and managed at a higher level.
​

From this view, you’ll see both the default post types and any custom post types that have been created. While it may look familiar, changes made here can control how post types behave across locations.

In general, it’s best to create and manage custom Feed post types from the enterprise level rather than building them separately at individual sites. Managing them here helps prevent duplicate post errors and keeps naming, visibility rules, and usage settings consistent. For step by step instructions, take a look at our article.

When it comes to default post types, enterprise settings establish the standard across locations. Individual sites can still enable default post types within their own Feed settings if needed. So if a default post appears active at a specific location after being turned off here, that location has likely turned it back on locally.

For shared custom post types, any edits to the name, icon, or settings will apply to every location the post is assigned to. If different sites need slightly different versions, separate custom post types should be created and assigned accordingly.