# Organizations, accounts and properties

Everything in AdPix sits under three levels — organization, account, property — and a fourth beneath them: the data stream. Where a setting lives, and who can change it, follows from that shape.

## Four levels, not three

The AdPix structure is always the same:

**organization → account → property → data stream.**

- **Organization** is the top level and the data boundary. Yours is created when your account is opened, and you own it. Every event carries an organization id and a property id, and every report query is bounded by both.
- **Account** is an organizing layer: it groups properties. If you run an agency or several brands, the account is where you draw the line between teams.
- **Property** is the reporting unit. Everything you see in a report belongs to one property, and the picker at the top of the console switches between them.
- **Data stream** is one input into that property — a website or an app. The measurement ID belongs to the stream, not to the property.

## What is defined at each level

| Level | What lives here | Minimum role to change it |
| --- | --- | --- |
| Organization | Organization-level members, organization settings, permanent erasure of one person's data | Org owner |
| Account | Account name, account members, creating properties, deleting and restoring properties, Trash | Account admin |
| Property | Name, primary domain, time zone, attribution window, excluded CIDRs, events and key events, custom definitions, cookie consent | Editor (property members: property admin) |
| Data stream | Measurement ID, collection mode, domain and cross-domains, write keys | Editor |

A property's plan — Free or Premium — is not in that list, because AdPix sets it, not the people in your business. Its effect is covered in [roles and data restrictions](concepts/governance/roles-and-data-restrictions).

## Access flows down the chain

Membership can be granted at any of the three levels. A person's effective authority on a property is the **highest** of what reaches them by three routes: a membership on the property itself, on the account above it, and on the organization.

The practical consequence: an organization-level membership means access to every property you have today and every property you create tomorrow. If someone should see exactly one property, grant the membership on that property.

In the access panel, rows that arrive from a higher level are marked **inherited** and are managed where they were granted — not here.

> **The property is the real data boundary**
>
> No report ever reads past the organization and property it was asked for. That bound is written into the database query itself, not into the interface — so even a hand-made API call cannot return another property's data.

## What cannot be undone

Most things here are reversible: names can be changed, deleted properties and accounts go to Trash and come back, roles can be taken away. These four are the exceptions:

> **Read these four before you create anything**
>
> - **A property's place is fixed.** It stays in the account it was created in; there is no way to move it to another account or organization.
> - **Reporting currency is chosen only when the property is created.** It is not editable in Property details.
> - **Deleting a data stream is final.** The stream and its keys are removed and the measurement ID does not come back. Past events stay where they are, but the tag installed on your site no longer reaches this property with that ID.
> - **Erasing one person's data has no undo.** The path is described in [data retention and deletion](concepts/governance/data-retention-and-deletion).

## Two property settings that also change the past

**Time zone** does not only affect new data. Every window bound and every day, hour, week and month bucket in the reports is evaluated in the property's time zone, so changing it re-buckets the whole history. Yesterday's numbers will move.

**Excluded CIDRs** work the other way round: matching requests are dropped before anything is written, so they only clean going forward. Internal traffic already recorded does not leave the reports when you add a CIDR.

## Where you see this in the console

1. Open Admin in the console.
2. Under Account settings, **Account details & hierarchy** shows the organization → account → property tree, and lets you create a new account or property from the same place.
3. Under Property settings, **Property details** opens the property-level settings and **Data streams** opens the streams.
4. **Account access management** and **Property access management** list the members at each level.

If you have not created a property yet, start at [create an account and a property](analytics/start/create-account-and-property); if the property exists but no data arrives, go to [install the tag](analytics/start/install-the-tag).

## Frequently asked questions

### What is the difference between an organization and an account?

The organization is the top level and the data boundary - every event carries its id and no report ever reads past it. An account is only an organizing layer inside that organization - it groups properties so you can grant access to a group of them at once.

### One property for my site and app, or two?

If you want their numbers read together, create one property with two data streams under it. Events do not carry a stream id, so every stream of a property rolls up into the same reports. If you want them reported separately, create two properties.

### Can I move a property to another account?

No. A property stays in the account it was created in, and there is no path to move it. If the structure is wrong, create a new property and point the tag at it - the old property's history does not come with it.

### Does deleting a property delete its data?

No. Deleting a property or an account is a soft delete - it moves to Trash, drops out of the lists, and an account admin can restore it. The recorded events are untouched. Actually removing data is a separate path.

## Related

- [Manage organizations, accounts and properties](https://docs.adpix.io/en/analytics/admin/organization-account-property/)
- [Organizations, accounts and properties](https://docs.adpix.io/en/account/teams/organizations-accounts-and-properties/)
- [Roles and data restrictions](https://docs.adpix.io/en/concepts/governance/roles-and-data-restrictions/)

---

[Docs](https://docs.adpix.io/en/concepts/foundations/organization-hierarchy/) · AdPix