---
title: "[AM2.0] - What’s Changed for Admins and Developers"
description: Changes in AM2.0 affecting admins and developers, including asset organization, governance, permissions, and stack-to-space linking.
url: https://www.contentstack.com/docs/assets/whats-changed-for-admins-and-developers
product: Contentstack Assets
doc_type: article
audience:
  - admins
  - developers
  - asset-managers
version: AM2.0
last_updated: 2026-03-25
---

# [AM2.0] - What’s Changed for Admins and Developers

This page explains what changed in Contentstack Assets AM2.0 for admins and developers, focusing on how assets are organized, governed, and reused across stacks and spaces. Read this when you are planning migrations, updating governance/permissions, or implementing cross-stack asset reuse.

## What’s Changed for Admins and Developers

Contentstack Assets rethinks how assets are organized, governed, and reused across Contentstack. Instead of being tightly coupled to individual stacks, assets are now managed in a dedicated system designed for scale, reuse, and intelligent discovery.

This shift benefits everyday users, admins, developers, and asset managers in different but meaningful ways.

Better separation between CMS and assets:
- Asset permissions are managed independently from CMS content roles.
- This avoids over-permissioning users who only need asset access.

New Assets Hub section in stack settings:
- Stacks can now be linked to one or more spaces.
- Assets are consumed by stacks, not owned by them, enabling true cross-stack reuse.

Contentstack Assets treats digital properties as a first-class system, not a side feature of CMS, making assets easier to find, reuse, and govern, while supporting real-world use cases like multi-site reuse, campaigns, and localization; this scales cleanly for growing teams and complex organizations, making it not just an upgrade, but a foundation for managing digital assets at scale.

## Common questions

### Do stacks still own assets in AM2.0?
No. Assets are consumed by stacks, not owned by them, enabling true cross-stack reuse.

### How are permissions handled differently in AM2.0?
Asset permissions are managed independently from CMS content roles, which avoids over-permissioning users who only need asset access.

### Where do I configure stack-to-space linking?
In the new Assets Hub section in stack settings, where stacks can be linked to one or more spaces.

### Who benefits from this change?
Everyday users, admins, developers, and asset managers benefit in different but meaningful ways.