Why Can't I Add a Component? (Private Beta)

Your instance's administrators can decide who can add each component to a page, and where it can go. This keeps pages consistent: a hero component that only belongs in the hero zone, for example, or a component only the design team places. So if a component you expect isn't there, or won't go where you want it, a visibility rule is usually the reason.

What you might notice

• A component is missing from the component list. You can't add it to this page: it's limited to certain people, sitemaps, page models or zones, or it's been disabled.
• Choose Zone doesn't list every zone. The component is only allowed in the zones shown.
• A zone won't accept a component when you drag it there. The component isn't allowed in that zone.
• Copy Component doesn't offer every zone. Only the zones the component is allowed in on the target page are listed.
• Changing the page model is stopped, with a list of components. Those components aren't allowed in any zone of the new page model.

If Agility refuses a change, the message tells you why, for example The "Hero" component isn't allowed in the "Main Content" zone of the "Landing Page" page model.

What isn't affected

Components that are already on a page keep working. They still appear on your website, and you can still edit them, reorder them in their zone, and remove them. Rules only apply when a component is added, moved to another zone, or copied.

What to do

Place the component somewhere it's allowed, or use a different component. If you think you should be able to add it, ask an Administrator, Manager or Designer on your instance. They can see and change the rules on the component model's Visibility pane (Component Visibility).

Related

• Add or Remove a Component
• Component Visibility