Social feed of the team's activity. Also, audit log.

mariusandra commented 2 years ago

Is your feature request related to a problem?

It's hard to keep track of what the team is using PostHog for. When I load the app, I see what insights have been recently modified, but nothing about any other part of the app. Did someone clean up dashboards? Are there any new feature flags that are now in use? Any recent annotations that mark exciting developments I should be aware of?

Describe the solution you'd like

As the homepage of the app, show a "social feed" (think FB/LinkedIn) of the team's activity.

Describe alternatives you've considered

Manually open dashboards, insights, feature flags, cohorts, annotations, and plugins. When possible, sort by last updated. Look through the list, and notice any new stuff.

Additional context

The "feed" is a fancy way of showing the data, but this ties in to a bigger notification and history system.
The idea came from reviewing this PR: https://github.com/PostHog/posthog/pull/8081 , where we're adding a "verified" tag to event definitions. This is yet another "bool", "bool_at", "bool_by" field combo in the system. The history system, if implemented, would track changes here. However getting a feed out of raw data like that will be costly. We need custom events, or to preprocess the raw data into something that can be used (edited these 3 fields --> "verify event").
I've heard the word "audit log" thrown around in reverence a few times. Should we get serious here?
If we want to get very Meta with our feed, we could use PostHog to log these events, and a plugin to preprocess them.

clarkus commented 2 years ago

I like this idea a lot. I've been thinking about a concept like this for summarizing the recent activity of a project, an organization, etc. This would also give us a meaningful landing page for onboarding new users.

pauldambra commented 2 years ago

linked to: #7819

jamesefhawkins commented 2 years ago

Just a thought - I can see features that are similar here with two quite different purposes:

feed = more discoveries - probably wise to make open source (so we get more users per org, which means more word of mouth growth and more revenue since bigger teams will then require ie user permissions)
audit log = data quality / debugging / security in an enterprise

clarkus commented 2 years ago

Agree with @jamesefhawkins - another way to think about this is with scopes:

Describing the activity for a container (organization, project, etc). The job here is to expose the recent activity for all the things users are doing within the container - For example: creating new insights, inviting new team members, concluding an experiment, etc. These are very much socially driven. We want users to notice this new stuff, go check it out and maybe even collaborate.
Describing the activity for a specific object. This could vary based on the thing being described. Example cases could include: billing history, audit log of membership changes for an organization, edit / sharing / etc history for an insight, the audit history for an experiment, etc. This case should probably be more inclusive with its logging.
With both instances, we'll probably want to provide some basic filtering or tuning controls so that users are seeing what is most valuable to them.

paolodamico commented 2 years ago

Highly aligned with @jamesefhawkins's comment, we should be very explicit about the specific problem we're trying to solve here. Based on a conversation last Fri with @mariusandra, I think it makes sense to build the backend functionality to track model changes and initially only consider user exposure to solve for the "audit log" problem.

This as a "social" feed will likely be highly valuable, but requires a lot more exploration first. Let's chat about this separately.

clarkus commented 2 years ago

Concept for a simple history of user actions for a given item. In this case it's an insight, but this could also describe a project, a dashboard, etc.

History

https://www.figma.com/file/NHPA2hVWwaKp4eTGWdigs9/Product-Concepts?node-id=1172%3A6252

sama8 commented 2 years ago

If relevant, we might be able to help. @BoxyHQ we help startups enable enterprise features in any SaaS app with just a few lines of code; including audit logs. https://github.com/boxyhq/hermes

posthog-bot commented 7 months ago

This issue hasn't seen activity in two years! If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in two weeks.

PostHog / posthog