--- canonical: https://amplience.com/developers/docs/platform/settings/content/ title: Content settings platform_badge: next-gen-app - User guides (new platform) description: Set up extensions, workflow statuses and locales in the Amplience Content Operations Platform to support the way your team creates content. audience: Administrator image: https://cdn.media.amplience.net/i/ampproduct/settings-content-workflow-1?w=1200&h=630 image_width: 1200 image_height: 630 date_published: 2026-10-30 date_modified: 2026-10-30 --- # Content settings Content settings control the tools, statuses and locales your team uses when creating content. Most are set up once by an administrator, then updated as your needs change. In the Content section of [Settings](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/platform/setup/), you can configure extensions, workflow statuses and locales. ![Amplience platform Settings, listing the content setup options](https://cdn.media.amplience.net/i/ampproduct/settings-content-workflow-1?w=1880&fmt=png 'Amplience platform Settings, listing the content setup options') > **Note:** To create or manage content repositories, use the classic platform. See [Content repositories](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/accounts/repositories/). ## Extensions Register extensions to add custom field editors, content editors and dashboards, so your team can work with content in a way that fits your processes and integrations. ## Workflow statuses Workflow statuses let teams track content as it moves through your production process, such as review or translation. You can create up to 100 statuses per hub, each with its own label and color, and assign them to content items and slots. Statuses are labels only. They don't block any actions, for example publishing, or enforce an order of steps. > **Info: Before you start** > If **Workflow statuses** isn't available in your **Settings**, contact your Customer Success Manager to enable it on your hub. ### Add a workflow status In **Settings**, choose **Workflow Statuses** from the Content section. ![Amplience platform Settings with Workflow statuses highlighted in Content section](https://cdn.media.amplience.net/i/ampproduct/settings-content-workflow-1?w=1880&fmt=png "Amplience platform Settings with Workflow statuses highlighted in Content section") On the **Workflow Statuses** page, click **Create Workflow Status**. Enter a label and choose a color, then click **Create**. > **Tip:** Developers can [set up webhooks](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/integrations/webhooks/) to send notifications when content status changes. ### Edit a workflow status You can change the label or color of a status. Any changes you make are applied to all content items and slots that already use the status. > **Note:** You can't currently delete a workflow status. ## Locales Locales are associated with **hubs** and are used for both field level and content item localization. See [Localizing content](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/user-guides/produce-content/localize/). A locale is a combination of a mandatory language code and optional country code. Locales can also have optional [labels](#locale-labels), which let you give them meaningful, easily identifiable names. ### Locale labels A locale label is an optional description that makes a locale easier for your content teams to recognize in a list. Without one, the locale code is shown instead. The field accepts emojis, so you can use your operating system's emoji picker (for example, right-clicking in the field). > **Tip:** Labels also help when locales stand in for something other than language, such as brands. For example, if `en` is Acme and `en-GB` is Globex, labelling them with the brand names is clearer than the codes alone. ### Add a locale > **Note: Before you start** > Locales are hub-specific. Check which hub you're using in the top-right of the window. In **Settings**, choose **Locales** from the Content section. Click the **Locales** button and choose the language code and optionally, the country code and a label. ![Amplience platform showing Locale settings page with a new locale being added](https://cdn.media.amplience.net/i/ampproduct/settings-content-locales-1?w=1880&fmt=png 'Amplience platform showing Locale settings page with a new locale being added') > **Note:** The first locale you add becomes the master locale, which is used by default for cards and previews in the content library. You can't delete it or make a different locale the master, so choose it carefully. Every other locale can be added, edited and deleted. Sometimes the same language needs different content in different countries. Portuguese for Portugal (`pt-PT`) and Portuguese for Brazil (`pt-BR`) are separate locales, so you set both a **Language** and a **Country**. > **Tip:** Using country flags in locale labels helps your team identify locales at a glance. ## Webhooks Webhooks are set up in the classic platform. See [Webhooks](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/integrations/webhooks/). ## Related pages [Setting the workflow status of content](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/platform/user-guides/content/track/#set-content-workflow-status) [Localizing content](https://amplience-developer-portal-git-develop-amplience.vercel.app/developers/docs/user-guides/produce-content/localize/)