Skip to content

Commit bc19ea3

Browse files
Update event-approval.mdx (#1842)
* Update event-approval.mdx Updated where to find Event Approval * grammar --------- Co-authored-by: myronkaifung <97630035+myronkaifung@users.noreply.github.com>
1 parent b29ddd7 commit bc19ea3

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

pages/docs/data-governance/event-approval.mdx

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,16 +8,16 @@ import { Callout } from 'nextra/components'
88

99
## Overview
1010

11-
Event Approval is a Data Governance feature for organizations that want visibility and control over all new events being sent to their Mixpanel project. The feature is a project-level setting that hides new events by default and notifies admins when those new events come in so they can then mark it as visible for everyone to see.
11+
Event Approval is a Data Governance feature for organizations that want visibility and control over all new events sent to their Mixpanel project. The feature is a project-level setting that hides new events by default and notifies admins when those new events come in, so they can then mark them as visible for everyone to see.
1212

1313

1414
### Enabling Event Approval
1515

16-
To enable Event Approval, navigate to the Project Settings page, scroll down to the Data Governance section under Overview and click the Event Approval toggle.
16+
To enable Event Approval, navigate to Lexicon, scroll to Event Approval under the Data Governance section, and click the Event Approval toggle.
1717

1818
When enabling this setting, input email addresses or aliases to be notified when a new event is ingested. Admins can also set up a Slack channel to be notified when a new event is ingested.
1919

20-
You can also enable new property detection, which will notify the same email addresses or slack channels about new properties that have been detected on new or existing events.
20+
You can also enable new property detection, which will notify the same email addresses or Slack channels about new properties detected on new and existing events.
2121

2222
Notifications are sent once per day. If multiple events are implemented in a project within one day, the notification will batch all these events.
2323

@@ -30,7 +30,7 @@ Only Project Admins or Owners can enable this setting, and it's only available o
3030

3131
When an admin receives a notification that new events have been ingested, they can click the "View New Events" button, which will take them to a Lexicon view of hidden events. New events will have a "New" tag and be sorted to the top of the list.
3232

33-
From there, an admin can take any number of actions such as marking the event as visible, adding a description or a tag.
33+
From there, an admin can take actions such as marking the event as visible, adding a description, or a tag.
3434

3535
Events will be marked as "New" as long as the following criteria are met:
3636
- It hasn’t been modified
@@ -44,4 +44,4 @@ If new property detection is enabled, notifications will also include a "View Ne
4444

4545
### Additional Notes
4646
- Please note that all [custom properties](/docs/features/custom-properties) will **not** be marked as "New"
47-
- Event Approval is not available for projects with > 3000 hidden events and will be auto-disable if projects exceed this limit
47+
- Event Approval is not available for projects with > 3000 hidden events and will be auto-disabled if projects exceed this limit

0 commit comments

Comments
 (0)