# Manage organizations, accounts and properties

The three-level structure lives in one Admin panel. This page covers what you can still change afterwards, what is locked the moment you create it, and exactly what deleting a property removes — and what it leaves alone.

## This page is about doing it, not about the model

The three-level model — organization → account → property → data stream — and why it works that way is covered in [organizations, accounts and properties](concepts/foundations/organization-hierarchy). This page only says where each action happens in the console, what is reversible and what is not.

## Where in Admin this happens

Open **Admin** from any page. The left rail carries three groups — **Global**, **Account**, **Property** — with the total number of settings open to you beside the heading. Above the rail is a search field (**Search settings**, shortcut `⌘K`) that matches on setting names, and **Back to reports** returns you to the reporting side.

> The Admin screen and its Global / Account / Property scopes. — [analytics.adpix.io/en/admin](https://analytics.adpix.io/en/admin)

Three items in the **Account** group concern the structure itself:

| Item | What it does |
| --- | --- |
| **Account details & hierarchy** | View the organization → account → property tree, create accounts and properties, and pick the active property |
| **Account access management** | The account's members and their roles |
| **Trash** | Items that have been soft-deleted |

Each has a direct link: `/admin?sel=hierarchy`, `/admin?sel=account-access` and `/admin?sel=trash`.

> **The rail opens on your highest role**
>
> Which groups you see is decided by the **highest role you hold anywhere** in AdPix, not by your role on the active property. The **Global** group is for AdPix platform administrators only, **Account** appears for account admin and above, **Property** for property admin and above. The action itself is checked again against the specific account or property — seeing an item does not guarantee you may use it everywhere.

## Create an account or a property

**Account details & hierarchy** shows the tree under the heading **Organizations, accounts & properties**. Each organization carries a **+ Account** button, each account a **+ Property** button.

1. Go to **Admin** → the **Account** group → **Account details & hierarchy**.
2. For a new grouping, select **+ Account** on the organization and give the **New account** dialog an **Account name**.
3. For a new reporting unit, select **+ Property** on the account and give the **New property** dialog a **Property name**.
4. Select **Create**. The confirmation points you at the next step: setting up the data stream.
5. Select **Select & set up tag →** on that property to make it your active property and land straight in **Data streams**.

Both actions — creating an account and creating a property — require account admin or above. A property admin or an editor cannot create a property.

A brand-new property has no domain yet; the real domain is written when you create its first data stream, and until then the list shows a placeholder in its place. The full path from nothing is in [create an account and a property](analytics/start/create-account-and-property).

## What you can still change afterwards

| What you want to change | Where | Minimum role |
| --- | --- | --- |
| Property name | **Property details** → **Basics** | Editor |
| Reporting time zone | **Property details** → **Basics** | Editor |
| **Attribution window** | **Property details** → **Basics** | Editor |
| **Excluded CIDRs** | **Property details** → **Traffic filtering** | Editor |
| Domain and cross-domains | **Data streams** → the stream | Editor |
| Account name or organization name | Not in this panel | — |

If your role cannot edit, the form still opens but carries the line "Read-only — your role can view but not edit these settings." and the **Save changes** button is not rendered at all. Field-by-field detail is in [property settings](analytics/admin/property-settings).

The one people discover late: **account names and organization names cannot be edited from this panel.** The tree only displays and creates. The organization name is written during initial setup and cannot be changed from the console afterwards.

> **The time zone moves the past too**
>
> The time zone does not only affect future data. Every date range and every day, hour, week and month bucket in every report is evaluated in this property's time zone, so changing it re-buckets the whole history and yesterday's numbers will shift. Get it right once.

## What is locked at creation

Three decisions are made the moment you create, and there is no way back:

- **Where the property sits.** It stays under the account it was created in, and that account under its organization. No move action exists — not in the console, not in the API.
- **The currency.** The only place the reporting currency can be chosen is the onboarding wizard, when the first property is created; a property created from this tree gets the default. **Property details** has no field for it and the save request never carries the value, so it cannot be changed afterwards.
- **The property ID.** The identifier used in URLs, keys and server-to-server requests is fixed and does not change when you rename.

> **Moving means starting over**
>
> If you later find that a property belongs under a different account, the only route is a new property under the right account with the tag pointed at it. The event history stays with the old property and is not transferred, so your reports split in two on that date. Sketch the account structure once before you create real properties.

## Delete, Trash, and what is not removed

Deleting a property or an account is **soft**: the row moves to Trash and an account admin can bring it back. Recorded events are untouched.

Open **Trash** from the **Account** group. The table — headed **Trash (soft-deleted, restorable)** — lists each item's type, name and deletion time, with **Restore** beside every row. Restoring takes effect immediately and the property returns to the tree.

Three things not to confuse with deletion:

- **Collection does not stop.** The tag on your site keeps sending events after the property is deleted, and those events are still written. To actually stop collection, remove the tag from the site or delete the data stream.
- **No data is erased.** Deleting a property is an organizing action, not a purge. Actually erasing data is a separate path, described in [data retention and deletion](concepts/governance/data-retention-and-deletion).
- **Deleting a data stream is final.** Unlike a property, a stream does not go to Trash: it and its keys are removed and its measurement ID does not come back.

> **Trash is an account admin surface**
>
> Both viewing Trash and restoring from it require account admin or above, and the list only covers organizations you actually administer. If you are a member but not an account admin, the item does not appear in the rail at all.

## Every change here is recorded

Every creation, rename, settings edit, deletion and restore writes a row to the audit log — with the real user, and, if someone acted on your behalf, that person recorded separately.

For a single property you read those rows in **Admin** → **Property change history**: time, actor, acting as, and action. When a number in a report suddenly moves, look here first — usually someone changed the time zone or the attribution window.

## Next

Once the structure is settled, add people: [roles and capabilities](analytics/admin/roles-and-capabilities) says what each role can actually do, and [invite people and SSO](analytics/admin/invite-people-and-sso) says how an invitation turns into access.

## Frequently asked questions

### How do I move a property to a different account?

You cannot. A property stays under the account it was created in, and there is no move action — not in the console and not in the API. If the structure is wrong, create a new property and point the tag at it; the old property's history does not come with you.

### Why is there no currency field in Property details?

Because it is written only at the moment the property is created — and only the onboarding wizard offers the field; a property created from the hierarchy tree gets the default. The settings form has no field for it and the save request never carries the value. Revenue in reports is read in the currency your events carry.

### Why does no group open for me in Admin?

The Account group appears for account admin and above, the Property group for property admin and above. An editor can change property settings but does not see this panel. Ask your account admin to raise your role.

### Does deleting a property stop collection?

No. Deleting moves the property to Trash, but the tag installed on your site keeps sending events and those events keep being written. To actually stop collection, remove the tag from your site or delete its data stream.

## Related

- [Organizations, accounts and properties](https://docs.adpix.io/en/concepts/foundations/organization-hierarchy/)
- [Create your account and property](https://docs.adpix.io/en/analytics/start/create-account-and-property/)
- [Property details](https://docs.adpix.io/en/analytics/admin/property-settings/)
- [Roles and capabilities](https://docs.adpix.io/en/analytics/admin/roles-and-capabilities/)

---

[Docs](https://docs.adpix.io/en/analytics/admin/organization-account-property/) · AdPix