I wouldn’t treat “one flow or one flow per role?” as a strict either/or.
WordPress’s own permissions model gives quite a useful way of thinking about this. A role is basically a bundle of capabilities; when WordPress needs to know whether somebody can actually do something, the useful question is the capability and sometimes the particular object/context—not merely the role name.
I think onboarding benefits from the same approach. Have one underlying onboarding system, but make its steps conditional on what this user can do, what state the account is in, and what their next useful task is.
So an admin might branch immediately into workspace setup and invitations, a team member into completing their first real task, and a viewer into finding and understanding the information they’ve been invited to see. Shared steps can remain shared; there’s no need to maintain three completely independent journeys.
It also means you can progressively reveal things. If the viewer can’t configure the workspace, don’t teach or foreground those controls. If a team member later gets a new capability, introduce the relevant feature then rather than making them sit through it during initial onboarding.
On WordPress I’d also be inclined to branch on capabilities rather than hard-coded role names wherever the distinction represents an actual permission. If BuddyPress Member Types are being used, those can describe what sort of member someone is, while capabilities describe what they can do. Those are usefully different questions.
So I’d probably describe the architecture as shared flow + conditional modules, rather than either “one onboarding for everybody” or “one completely separate onboarding per role.”
Error 404 - Destination Not Found
1.2 1.5 1.6 1.7 1.8 1.9 2.0 2.1 2.3.0 2.4.0 2.5.0 2.6.0 2.7.0 2.8.0 5.0.0 6.0.0 7.0.0 8.0.0 10.0.0 12.0.0 14.0.0 attachments beta Beta2 BuddyCamp BuddyPress Template Pack classic codex Contributor Day contributors developers features feedback future maintenance rc-1 release candidate releases rewrites roadmap security support Survey uses wordcamp
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Comment on DEV: The Bug Stops Here by Grain de Magie | 0 | 11.5 | 05-08-2026 |
| 2 | How to manage a staff member wanting to implement multiple Claude written applications? | 0 | 5.93 | 10-08-2026 |
| 3 | Send new user ‘…would like to join…’ emails to specific admin users | 0 | 7.54 | 28-07-2026 |
| 4 | Droptica: Content personalization in Drupal, part 2: journeys and smart forms for multiple audiences | 0 | 7 | 14-07-2026 |
| 5 | 8 Reasons I Recommend Squarespace Premium | 0 | 10.21 | 26-06-2026 |
| 6 | Scrum Isn't for Stormtroopers | 0 | 15.26 | 28-07-2026 |
| 7 | Password issue after bp_core_signup_user() | 0 | 5 | 27-02-2026 |
| 8 | Как написать сильный кейс о незавершённом проекте? | 0 | 8 | 27-06-2026 |
| 9 | “Scrum didn’t work for us.” | 0 | 8.1 | 30-07-2026 |
| 10 | Вы не отказываетесь от системы. Вы отказываетесь от понятности. Когда ... | 2 | 6 | 27-06-2026 |