Requirements and UX for a secure, efficient User Management system in SpotGenius: user roles, permissions, authentication, authorization and multi-tenancy. Users with access to more than one organization could see data across all of them, which is a privacy risk. The new system introduces role-based access and proper data segregation.
Every user was assigned a single role at the profile level, and that role applied to every organization they belonged to.
Users with access to several organizations had no separation between them. Data from different customers could mix in reports and views, which is both a security concern and an easy way to make mistakes.
The permission model everything else sits on: where does a user's role live?
One role applies to every org they can access.
Admin in one org, Viewer in another, data kept apart.
Why: Users who work across several customers need different rights in each, and each customer's data must stay separate. Attaching the role to the organization membership fixes both.
I defined personas for each user type to pin down what each one needs to do and where they should stop.
“Managing different organizations and the users within them. Troubleshooting technical issues.”
Customer success. Onboards new customers, sets up their parking lots and troubleshoots when they have issues.
“I'm in the field, setting up SpotGenius for our customers.”
Installation specialist who sets up SpotGenius at customer lots and uses SG Admin to configure the lots they're working on.
“Managing my organization's users and parking lot settings.”
The highest role inside their own organization. Manages settings for the organization's lots.
“Access reports and the DigiMap. No access to lot settings or the users page.”
Uses SpotGenius to monitor lots and pull reports.
Accounts are created by an admin rather than through self sign-up. The flow takes a new user from the admin's invite to an activated, configured account.
Roles are split into SpotGenius users and customer users. Instead of one role on the profile, a user belongs to one or more organizations and gets access to specific parking lots within each one, so data stays separated by organization.
Password protected97 accounts and $1.91M ARR adopted it in the first 30 days
$1.91M ARR across adopting accounts
Password protectedSetting the direction for Albi's AI agents: one guided agent now, a marketplace later