As an editor, I want to be able to make a copy of another council’s flows so I don’t have to build a new service from scratch (done ✅)
As an editor, I do not want people from outside my team to be able to edit my flows, as this is a legal liability and security risk for my council (done ✅)
As a team admin, I want to be able to add or remove team members and team settings myself (done ✅)
Plan✕ has a role-based access control (RBAC) model which allows authorised users of the Editor to interact with services based on their roles.
An authorised user is an individual who signs into the Editor using their email.
A team is a group that a set of flows or services belong to. Teams are most often synonymous with a council but not exclusively. Each team has settings that include its logo, theme colour, custom subdomain, and other attributes.
Each user is often a Team Editor of at least one team, and may be part of many teams with different roles.
As PlanX is a collaborative, multi-tenant environment, all users are by default a Team Viewer.
| Role | Team Viewer | Team Editor | Team Admin |
|---|---|---|---|
| Can view any team’s flows | ✅ | ✅ | ✅ |
| Can view any team’s settings | ❌ | ❌ | ❌ |
| Can view any team’s submissions | ❌ | ❌ | ❌ |
| Can view any team’s feedback | ❌ | ❌ | ❌ |
| Can view any team’s members | ❌ | ❌ | ❌ |
| Can view any team’s subscription | ❌ | ❌ | ❌ |
| Can add, update, archive, publish own team’s flows | ❌ | ✅ | ✅ |
| Can add, update, remove own team’s settings | ❌ | ✅ | ✅ |
| Can view, download own team’s submissions | ❌ | ✅ | ✅ |
| Can view, download own team’s analytics | ❌ | ✅ | ✅ |
| Can view, action own team’s feedback | ❌ | ✅ | ✅ |
| Can add, update, remove own team’s members | ❌ | ❌ | ✅ |
| Can view own team’s subscription | ❌ | ❌ | ✅ |
✅ = has permission, ❌ = does not have permission, 🔮 = will have permission in future when implemented
Coming soon: Stripe
Coming soon: technical implementation details about JWTs and Hasura
Platform Admin