mixpanel · myronkaifung · Jul 1, 2024 · Jul 1, 2024 · Jul 1, 2024 · Jul 1, 2024
@@ -1,4 +1,5 @@
 {
+    "login": "Login",
     "two-factor-authentication": "Two Factor Authentication",
     "single-sign-on": "Single Sign-On"
 }
@@ -0,0 +1,30 @@
+# Login
+
+## Overview
+
+Mixpanel users access Mixpanel's UI by authenticating through a login process. Mixpanel supports a few different methods for login.
+
+## Magic Link
+- is the default for all users when they sign up for a new account
+- Unless domain is claimed or other access security settings (see 2FA and SSO)
+- When you click sign in, an email is sent to the email associated with your account. Click the link in the email to login.
+
+## Password login
+- Can override default magic link login by navigating to Personal Settings and defining a password.
+- After defining a password, login defaults to password moving forward and magic link option will no longer be used.
+- Change password in the same personal settings page
+
+## Organization Access Security
+- org owners/admins can enforce requirements for access security to safeguard data.
+- 2FA: Whenever users sign in with a username and password, they also need to enter a security code generated on their mobile device. Users do not need a security code when signing in through the organization's identity provider (SSO).
+- SSO: Enable users of your organization to log in with single sign-on. Can also require users to login using SSO and assign roles/permissions via IdP.
+
+## FAQ
+
+#### Why am I not receiving the magic login link after I click in?
+Check the junk/spam inbox for the email or click the resend the email from the login page. 
+
+If you are not seeing the email even after checking spam and resending the email, it is possible that your account may be associated with a different email. In this case, try signing up for a new account using your provided email. If your account already exists, this is another way to send the magic login link to your email. If your account does not exist, it will create one for you.
+
+#### Why don't I see my team's data and reports?
+If you signed up via an invitation from a teammate, it is possible that the invitation was sent with the incorrect access permission. Reach out to your teammate and have them follow [these instructions to grant you access](/docs/orgs-and-projects/roles-and-permissions#invite-users).
@@ -1,7 +1,7 @@
 {
+    "lexicon": "Lexicon",
     "data-views-and-classification": "Data Views & Classification",
     "event-approval": "Event Approval",
     "data-volume-monitoring": "Data Volume Monitoring",
-    "lexicon": "Lexicon",
     "data-clean-up": "Data Clean-Up"
 }
@@ -88,6 +88,13 @@ If you have Group Analytics enabled, you will see a dropdown on the Profile Prop
 
 ![Lexicon Profile Properties](/lexicon-group-analytics-GIF.gif)
 
+### Lookup Table Definitions
+
+[Lookup Tables](/docs/data-structure/lookup-tables) in your project are listed in your Lexicon. Click into a Lookup Table definition to export the underlying CSV, replace the Lookup Table with a new CSV, and see which properties are linked.
+
+### Formulas and Behaviors Definition
+Saved [Formulas](/docs/reports/insights/metrics#formulas) and [Funnels/Retention Behaviors](/docs/features/saved-behaviors) in your project are also documented in your Lexicon. Review here to get an overview of existing definitions in your project that you can quickly leverage in your own analysis.
+
 ## Filtering Events, Custom Events, and Properties
 
 Lexicon provides several options for you to filter your events, custom events, event properties, and profile properties.
@@ -104,7 +111,7 @@ This data lets you easily discover the parts of your implementation that are mos
 
 ![Lexicon Query Volumes](/lexicon-query-volumes.png)
 
-## Dropping and Hiding Data
+## Dropping Data
 
 In Lexicon, you can intercept and drop incoming events or properties. Mixpanel won’t store any **new data** for the event or property you select to drop. **Warning: You cannot recover event data after you drop it.**
 
@@ -130,6 +137,16 @@ To drop an event in Lexicon:
 ![Lexicon Drop Events Warning](/lexicon-drop-events-warning.png)
 3. Click Drop. The status of the event indicates **Dropped**.
 
+**Undropping Events**
+
+You can undrop events and properties when you decide you need them again.
+
+To undrop an event:
+
+1. Select a dropped event. The “Status” column indicates if an event is dropped.
+![Lexicon Undrop Events](/lexicon-undrop-events.png)
+2. Click **Undrop**. The “Status” column no longer contains “Dropped”.
+
 ### Dropping Properties
 
 By dropping a property, you can intercept and drop incoming property. Mixpanel won’t store any new data for the property you select to drop. 
@@ -140,25 +157,25 @@ To drop a property in Lexicon:
 ![Lexicon Drop Properties](/lexicon-drop-properties.png)
 2. Click **Drop**. A warning indicates that you cannot recover the data that you choose to drop. Click Drop to confirm. The status of the property will indicate Dropped.
 
-### Undropping Events
+**Undropping Properties**
 
-You can undrop events and properties when you decide you need them again.
+1. Select a dropped property. The “Status” column indicates if a property is dropped.
+![Lexicon Undrop Properties](/lexicon-undrop-properties.png)
+2. Click **Undrop**. The “Status” column no longer contains “Dropped”.
 
-To undrop an event:
+## Hiding Data
 
-1. Select a dropped event. The “Status” column indicates if an event is dropped.
-![Lexicon Undrop Events](/lexicon-undrop-events.png)
-2. Click **Undrop**. The “Status” column no longer contains “Dropped”.
+In Lexicon, you can hide any events or properties. Unlike [dropping data](/docs/data-governance/lexicon#dropping-data), hiding data does not affect data ingestion; any events/properties that are hidden will continue to be ingested in your project and count toward your data allowance.
 
-### Undropping Properties
+A hidden entity will not be indexed in your event/properties menu in the query builder. Any [inactive events and properties](/docs/tracking-best-practices/debugging#inactive-events-and-properties) will also be hidden.
 
-1. Select a dropped property. The “Status” column indicates if a property is dropped.
-![Lexicon Undrop Properties](/lexicon-undrop-properties.png)
-2. Click **Undrop**. The “Status” column no longer contains “Dropped”.
+Hidden events will be excluded from your query results. For example, it will not be included in "All Events" and won't appear as an intermediate step in your [Flows report](/docs/reports/flows).
+
+Hiding data is useful for preventing not-so-commonly used entities from cluttering your events/properties menu, or to prevent certain events from being considered in your reports.
 
-### Hide Events and Properties
+If you wish to use a hidden entity in your report, you may manually select the entity by searching in the events/properties menu and then clicking "Show Hidden Events/Properties" to reveal the hidden entity.
 
-To hide an event or property:
+### Hiding Events and Properties
 
 1. Select one or more visible events, event properties, or profile properties. The “Hide” icon appears. You can check the “Status” field to determine whether an event or property is visible or hidden.
 ![Lexicon Hide Events](/hide-events.png)
@@ -188,25 +205,23 @@ Do note however that user profile properties cannot be merged at this time.
 
 ### Merging Events
 
-To merge events:
+**To merge events:**
 
 1. Select the events to merge. The “Merge” icon appears.
 2. Click Merge. The “Merge Events” window appears. It shows the events you selected and explains that merging the selected events combines them into a single event, which does not affect the raw data.
 ![Lexicon Merge Events](/lexicon-merge-events.png)
 3. In the “MERGE SELECTED EVENTS INTO…” section, specify which event Mixpanel should consider as the new unique event.
 4. Click **Merge**. The merged event appears and the “Status” column indicates “Merged”.
-
-### Unmerging Events
 
-To unmerge events:
+**To unmerge events:**
 
 1. Select the merged event to unmerge. The “Unmerge” icon appears.
 ![Lexicon Unmerge Events](/unmerge-events.png)
 2. Click Unmerge. The merged event appears as the original two distinct events.
 
 ### Merging Properties
 
-To merge properties:
+**To merge properties:**
 
 1. Select the properties to merge. The “Merge” icon appears.
 2. Click Merge. The “Merge Properties” window appears. It shows the properties you selected and explains that merging the selected properties combines them into a single property, which does not affect the raw data.
@@ -216,7 +231,7 @@ To merge properties:
 
 ### Unmerging Properties
 
-To unmerge properties:
+**To unmerge properties:**
 
 1. Select the merged property to unmerge. The “Unmerge” icon appears.
 ![Lexicon Unmerge Events](/unmerge-properties.png)

@@ -94,11 +94,11 @@ Then select the Projects tab.
 
 ## Manage Timezones for Projects
 
-Mixpanel records all events in [Coordinated Universal Time (UTC)](https://www.worldtimeserver.com/learn/what-is-utc/) at intake.
+>Note: For projects created before 11 Jan 2023, Mixpanel converts event timestamps to your project timezone before writing the event to your Mixpanel data stores, meaning that event timestamps are stored based on the project timezone setting at the time of ingestion.
 
-Mixpanel converts the timezone to your project timezone before writing the event to Mixpanel data stores. Mixpanel sets project timezones by city or region. If a city or region observes Daylight Savings Time, the ingestion offset adjusts appropriately.
+Mixpanel records all events in [Coordinated Universal Time (UTC)](https://www.worldtimeserver.com/learn/what-is-utc/) at intake. Changing the timezone for any project under Project Settings only affects the timezone in which Mixpanel outputs results.
 
->Note: As of 11 Jan 2023, all new projects store their data in UTC. Changing the timezone for any project under Project Settings only affects the timezone in which Mixpanel outputs results. You will no longer see a gap or spike in events after changing the timezone.
+Mixpanel sets project timezones by city or region. If a city or region observes Daylight Savings Time, the ingestion offset adjusts appropriately.
 
 ### Changing your Timezone
 
@@ -120,17 +120,9 @@ To change the project’s timezone:
 
 >Note that changing the timezone will not affect any data, it only affects the timezone in which we output results.
 
-### Understanding How Timezones Affect Data
-
-After you set your timezone correctly, you should send any dates or times to Mixpanel as Coordinated Universal Time (UTC).
-
-By default, Mixpanel’s integration libraries work with API ingestion endpoints to automatically convert the UTC timestamp or date to your project timezone before storing your data.
-
->If you overwrite the default timestamp, import old data, or set a property that is in date format (e.g. Account Created Date), be sure to send the timestamp or date in UTC.
-
 #### Sending Date Properties to Mixpanel
 
-As mentioned previously, you should send date properties to Mixpanel as UTC. Date properties are one of the five data types Mixpanel accepts.
+[Date properties are one of the five data types](/docs/data-structure/property-reference/data-type#date) Mixpanel accepts. Mixpanel events should be ingested with timestamps set to Coordinated Universal Time (UTC). If you overwrite the default timestamp, import old data, or set a property that is in date format (e.g. Account Created Date), be sure to send the timestamp or date in UTC.
 
 For this type of property, Mixpanel recommends an iso-formatted date string (YYYY-MM-DDTHH:mm:ss) to use in your Mixpanel reports.
 
@@ -156,28 +148,19 @@ Mixpanel.track("Account Created Date", props);
 ```
 #### Exporting Data from Mixpanel
 
-When you’re exporting raw data from Mixpanel, your request requires the date parameters "from_date" and "to_date" to determine which date range of data to return.
+When you’re exporting raw data from Mixpanel, your request requires the date parameters `from_date` and `to_date` to determine which date range of data to return.
 
 Mixpanel's raw export machines interpret the "from_date" and "to_date" values to your project’s timezone. As a result, if you request a single day of data, you receive one full day in your project’s timezone, not one full day in UTC.
 
-As mentioned earlier, Mixpanel hardcodes event timestamps to your project’s timezone. However, the "$time" property from a raw export returns with a Unix timestamp, not a UTC timestamp.
-
-The Unix timestamp represents the number of seconds that have elapsed since 00:00:00 on January 1, 1970 in your project’s timezone.
+As mentioned earlier, Mixpanel stores your events in UTC. The "$time" property from a raw export returns with a Unix timestamp, which represents the number of seconds that have elapsed since 00:00:00 on January 1, 1970.
 
-In the example below, if your project’s timezone is US/Pacific, the below parameters return:
-
-
-```
-00:00:00 Aug. 1 to 11:59:59 Aug. 1 PDT, or 07:00:00 Aug. 1 – 06:59:59 Aug. 2 UTC. from_date = "2015-08-01" to_date = "2015-08-01"
-```
+In the example below, if your project’s timezone is US/Pacific, and you set both the `from_date` and `to_date` to `2023-08-01`, it will return events between `00:00:00 Aug. 1 to 11:59:59 Aug. 1 PDT`/`07:00:00 Aug. 1 – 06:59:59 Aug. 2 UTC` where the events timestamp are in Unix timestamp format in UTC.
 
 #### Importing Data into Mixpanel
 
 Always send imported data to Mixpanel in UTC to ensure it displays correctly in your project.
 
-Mixpanel hardcodes timestamps of exported data to your project’s timezone. The exported data can be events and any date properties on events and users.
-
-As a result, operations such as extract, transform, and load, need a quick timestamp and date property offset to reset the data back to UTC before importing it back to Mixpanel.
+Mixpanel stores your data in UTC, then use your project timezone setting to output data in your selected timezone.
 
 ## Transfer Project to Another Organization
 

@@ -2,8 +2,12 @@
 
 
 ## Overview
+An Organization is an entity that links your projects, users, and subscription plan.
 
-As an Organization Admin, you may create and manage security processes that dictate the requirements needed for your users to access your organization.
+## Creating an Organization
+A user who signs up for a new Mixpanel account without being invited by an existing Mixpanel user will be prompted to create a new organization. This is the only way a new organization is created. 
+
+[Contact the Support team](https://mixpanel.com/get-support) if you need to create a new organization as a member of an existing organization.
 
 ## Organization Discoverability
 Organization Discoverability makes it seamless for new users with a shared work email domain to connect with teammates in an existing organization in Mixpanel, allowing them to access their team’s projects, data, and reports, instead of joining a new, empty org.
@@ -28,3 +32,11 @@ The org owner or admin can then designate the level of discoverability of their
 **Admin Approval:** An organization designated as requiring “admin approval” is discoverable to any new user signing up with a specified email domain, but can only be joined upon request. Admins will receive an email notification to authorize access.
 
 **Invite Only:** An organization designated “invite only” is undiscoverable regardless of email domain. New users must be invited by the admin.
+
+## Deleting an Organization
+
+Organization Owners may request the closure of the organization under the Overview tab in the Organization Settings, which would delete your organization, all existing projects, and all the data contained inside of the project. Users will maintain access to your organization for 90 days, after which it will be deleted. After 90 days, organization projects will be **permanently** deleted.
+
+Learn more about [privacy and compliance here](/docs/privacy/overview).
+
+[Contact the Support team](https://mixpanel.com/get-support) if you have any questions regarding the deletion of your organization/data.
@@ -1,10 +1,12 @@
 # Overview
 
 
-The Mixpanel administrative system includes organizations and projects.
+The Mixpanel administrative system includes organizations, projects, and teams.
 
 An **Organization** is the controlling entity that links projects, users, and a plan together. Each organization has a single Mixpanel plan associated with it and that plan is what determines the data volume limits and features available across all projects in the organization.
 
 A **Project** is a container for your product's analytics data, including saved entities like custom events, or saved reports. Projects house the events, properties and user profiles sent to them which can then be queried with Mixpanel’s web interface and APIs. A single organization can contain multiple projects and each project’s data tallies are summed together to give the organization-level usage.
 
+A **Team** is a group of users in your organization that shares the same project access permission, which makes it easier to manage roles and permissions for a group of users. A team contains a roster of users, the projects they are assigned to, the role permission in each project, Data View access, and Classified Data access. 
+
 ![Organization Overview 1 Image](/organization_overview.png)
@@ -44,7 +44,7 @@ If there are projects that you wish for everyone in your organization to have so
 
 ### Remove Users
 
-You can remove users from an organization or project.
+You can remove users from an organization or project. You can only remove users with role permission below your own.
 
 #### Remove User from an Organization
 
@@ -95,6 +95,8 @@ Paid Organizations have four roles: Owner, Admin, Billing Admin and Member. Free
 
 #### Owner
 
+>As a best practice, it is recommended to have at least 2 Organization Owners at all times, in case an owner loses access to their account or is no longer working with the company.
+
 Organization Owners have administrative permissions for the organization and all the projects in the organization. Multiple users can be Owners. However, each organization must have at least one Owner.
 
 #### Admin