> ## Documentation Index
> Fetch the complete documentation index at: https://docs.activeviam.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to manage market-data access

> Individual market-data environment assignments in the Admin console, with View, Edit, and Owner levels, immediate permission changes, and the different removal behavior of custom and default environments

Applies to **Admin** → **Market Data** for a selected active user.

Market-data permissions control access to named environments and their observations.
Viewing data, changing observations, and managing environment details require different access levels.
These grants remain separate from report and portfolio permissions.

## What is required before assigning access?

* Administrative access to the intended organization.
* Another active account in that organization.
* Access to the environment being assigned.
* An approved access level for the intended task.

The table lists environments available to the acting administrator.
A missing environment does not prove that the organization has no such environment.
For environment creation, see [Market data environments](../../user-guide/update-data/market-data-environments).

## Which access level is required?

| Level | Capability |
| - | - |
| **View** | View market data from the environment. |
| **Edit** | View data and perform supported observation updates. |
| **Owner** | Manage ownership-controlled actions, including custom-environment details and sharing. |

Changing an environment's name, description, or active status requires ownership.
**Edit** access does not provide those metadata controls.
View-only account roles receive viewing access rather than data-editing capabilities.

Permission assignment does not load market observations or start a download.
Data coverage and report availability must be checked separately.

## How to assign an access level

<Warning>
  Selecting an access level submits the change immediately.
  There is no separate **Save** or confirmation dialog for these permission changes.
</Warning>

1. Open **Admin**.
2. Select the target account in **Users**.
3. Check the selected name and email.
4. Select **Market Data**.
5. Locate the environment under **Provider Name**.
6. Check whether the environment is marked **(default)**.
7. Open the row's **Access Type** menu.
8. Select the intended **View**, **Edit**, or **Owner** level, where available.

Check the success or error alert after the table refreshes.
Verify the environment's resulting **Access Type**.
Then verify the intended market-data or report workflow using an approved test account.
A refreshed table alone does not confirm that the change succeeded.

## How do default environments differ?

| Environment | Access behavior |
| - | - |
| **Derivitec** default | Built-in viewing access; its permission control is disabled. |
| Organization default | Organization fallback access applies unless an individual override changes it. Owner is not offered. |
| Custom environment | Access normally comes from an explicit grant to the account. |

Removing a custom grant and blocking organization-default access are different operations.
The **Derivitec** default cannot be removed through this screen.
Removing one environment does not block access to every market-data source.

## How to remove a custom-environment grant

<Warning>
  **Remove Access** submits immediately and can affect reports that need the environment.
  It removes the selected grant; it does not delete the environment or its observations.
</Warning>

1. Open **Admin**.
2. Select the target account in **Users**.
3. Select **Market Data**.
4. Locate the intended custom environment without the **(default)** marker.
5. Open its **Access Type** menu.
6. Select **Remove Access**.

Verify the removal alert and the resulting access state after refresh.
If the environment remains accessible, removal has not been confirmed.
This check is particularly important for view-only accounts or accounts whose role has changed.
Escalate a failed removal to the configured support contact.

Check the affected account's workflow separately.
Removal does not retract previously downloaded files or already displayed data.

## What about organization-default access?

**Remove Access** on an organization default attempts to block that account's fallback access.
This differs from removing a custom grant.
Removal for a **View Only** account can be rejected and requires support review.
Do not treat a clicked menu item as successful revocation.

Changing the level later replaces the individual override with the selected access.
Confirm the resulting account behavior before relying on the change.

## What does Share With Organisation Admin mean?

The separate environment manager can offer **Share With Organisation Admin** to an environment owner.
That action grants eligible organization administrators and executives editing access when no existing grant is present.
Existing grants are retained.
It does not publish the environment publicly or grant access to every organization member.
Use the **Admin** → **Market Data** workflow for individual account assignments.

For related access requirements, see [Report access](./report-access) and [Portfolio access](./portfolio-access).