PostHog / PostHog/marketing

Messaging: review the access control migration notice email

Open
#337 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

messaging
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
8h 50m
Merged PRs (30d)
3

Description

Messaging

Context

We're changing how access control rules combine. When more than one rule applies to a user, we used to apply the highest access level. Now the most specific rule applies. RFC: https://github.com/PostHog/requests-for-comments-public/pull/557

New organizations already start on the new behavior, and organizations where nothing changes were migrated automatically. 87 customer organizations were left on the old behavior, because some of their users would lose or gain access. An org admin has to review and accept the change.

Affected orgs (there are large Enterprise customers): https://docs.google.com/spreadsheets/d/1cmILwDfwNcUCW6PhtGnPKLdXwjUIySNQwh1csT3QVvY/edit?usp=sharing

Org admins review it on a preview page in organization settings. It lists every person and object affected, and they accept the switch from there.
Preview page: https://github.com/PostHog/posthog/pull/88704

I built a one-off email in Workflows to point the admins of those organizations at the preview page. It is a draft: https://us.posthog.com/project/2/workflows/01a0b52b-2d7d-0000-b0bf-ce86bedb8a2c/workflow

I plan to message large orgs in Slack separately.

Format
  • Single email broadcast (e.g. a newsletter)
  • Multiple email broadcasts (e.g. a notification and reminder)
  • Automated email campaign (e.g. logic-based flow)
  • Requires in-app notification
  • Requires social media support

A Workflows batch send to a static cohort. The app already shows a banner in access control settings that links to the same preview page.

Timeline

Panned send date: Monday, Sept 21

Nothing changes for an org until an admin accepts, but if no one responds I'm thinking of adding a hard-cutoff date to finish the migration + send another notice.

Targeting

Org admins and owners of the affected orgs (125 people). They were picked from access control events and checked against current org membership. Only admins and owners can open the preview page, so members are not included.

Cohort: https://us.posthog.com/project/2/cohorts/579149

Subscription topic
  • Welcome emails
  • Changelog updates
  • Product notifications
  • Actually useful marketing emails
  • Service updates
  • All subscribed and unsubscribed users
Requested input and previews

Workflow:
https://us.posthog.com/project/2/workflows/01a0b52b-2d7d-0000-b0bf-ce86bedb8a2c/workflow

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Open the draft email in the linked Workflows page and compare it with the access-control context, RFC, and preview-page link. Review whether the notice accurately explains the migration and directs affected organization admins to the preview page; the work is done when the email is ready for the planned broadcast.

Written by the indexing model from the issue text.

Assessment

Domain
authorization, content
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.