---
title: Environment Admin
slug: docs/environment-admin
docTags: 
createdAt: 2023-11-27T18:35:55.113Z
---

To use an IMS organization or Experience Platform sandbox in **Demo System Next**, a user must be granted access. This access is managed separately from the underlying provisioning and permissions in **Adobe CX Enterprise**. In practice, that means the user must be assigned both the relevant **IMS organization** and the relevant **AEP sandbox** in Demo System Next, even if access has already been configured elsewhere, such as in **Quick Setup**.

There are two primary self-service tools:&#x20;

1. [IMS Org Admin](docId:1ATApfz9s07vwwdpxRkZ6) - allowing admins to add or update IMS Orgs and integration details
2. **Environment Admin** - allowing users to assign users to orgs and sandboxes.

## Environment Admin

[https://dsn.adobe.com/tools/environment-admin ](https://dsn.adobe.com/tools/environment-admin)(Legacy)

[https://livedemos.adobe.com/apps/dsn/environment-admin](https://livedemos.adobe.com/apps/dsn/environment-admin) (New)

![](https://api.archbee.com/api/optimize/bAgVaanSi1tFmfc8PghaH/Npzhyoo3g9ZGKgzVys7K0_cleanshot-2026-09-21-at-41619-pm-2x.png)

This view allows you to assign others to orgs as both users and admins, and specify which sandboxes should be visible for them in DSN. This affects which environments (org/sandbox) they can select in **Quick Setup** or view in the **Environment** list.

Removing a user (or self) from an org in this view unassigns them from the org altogether, so be careful not to remove yourself from an administered org by accident.

