Tenant Configuration

Tenant Configuration (Anthill-managed)

Activator is a multi-tenant platform. Some features, settings, and capabilities are configured at the tenant level by the Anthill team, rather than being available to all users universally. This article explains what varies per tenant, what you can see and control in the UI, and how to request configuration changes. 

What Can Vary Per Tenant

The following aspects of Activator can differ between organisations:

Roles and permissions

User roles (e.g. Designer, Reviewer, Admin) and the capabilities associated with each role can be configured per tenant. Not all roles may be available in your organisation, and the actions permitted under each role may differ from what is described in generic Activator documentation.

DAM connectors

Connections to Digital Asset Management (DAM) systems are configured at the tenant level. Your organisation may have one or more DAM integrations enabled, or none at all. The available asset sources shown in Activator will reflect your tenant’s configuration.

Mandatory fields and metadata

The fields that are required when creating or publishing content may be defined by your tenant configuration. Mandatory fields can vary — what is optional in one tenant may be required in another.

Publishing rules

Rules that govern when and how content can be published (e.g. approval workflows, CRM destination settings) are configurable per tenant. Consult your local guidelines or contact your Anthill representative for specifics.

Feature flags

Some Activator features are enabled or disabled at the tenant level. If a feature described in the knowledge base is not visible in your environment, it may not be enabled for your tenant.

Design System setup

The structure, naming conventions, and available elements within your Design System are set up per tenant. This includes the layout templates, component libraries, and asset folders available to your team. 

What You Can and Cannot See in the UI

As a general principle, Activator only displays options and settings that are available in your tenant. If a menu, field, or feature does not appear in your UI, it may simply not be enabled for your organisation — rather than being a bug or user error.

If you are unsure whether a feature should be available to you, contact your local Activator administrator or the Anthill support team before assuming it is a technical issue. 

Requesting Configuration Changes

Tenant configuration is managed by the Anthill team and cannot be changed directly by users. To request a change:

  • Include in your request: the specific setting or feature you need changed, the reason for the change, and any relevant deadlines or approvals.

  • Allow sufficient lead time — configuration changes may require review and testing before being applied to a production environment.

Important: Not all configuration changes can be accommodated. Some settings reflect platform-level design decisions or contractual scope. The Anthill team will advise on feasibility when you submit a request. 

Default vs Tenant-Specific Behaviour

When reading Activator documentation, be aware that descriptions of features or default settings may not match your tenant’s configuration. Activator does not have a single universal “default” experience — each tenant is configured independently.

If something in this knowledge base does not match what you see in Activator, the most likely explanations are:

  • The feature is not enabled in your tenant

  • Your tenant has a custom configuration for that setting

  • The documentation covers a newer version of Activator than your tenant is currently running

In any of these cases, contact your Anthill representative for guidance specific to your environment