Org structure that matches permissions.
Technicians, teams, and departments live beside the RBAC model that actually gates data access.
Org charts in HR tools do not keep customers safe. Core ties team structure to the same role and permission system that SecOps cares about—because that is what stops cross-tenant leaks.
People records
Technicians linked to real users.
Identity alignment. Map staff to Supabase users so audit trails and assignments resolve to a person.
Team groupings. Departments and teams model how work is routed and reported internally.
Technicians linked to real users.
RBAC backbone
Roles mean something at the database.
JWT claims + RLS. Policies reference tenant and permission claims—not just UI hiding buttons.
Least privilege defaults. Grant only the app_permission values each role truly needs.
- Role matches job function
- Customer scope limited
- Certifications tracked
Roles mean something at the database.
Operational use
Assignment and visibility follow org structure.
Ticket assignment. Route work to technicians your customers already know by name.
Reporting rollups. Slice metrics by team when you are coaching performance.
| Read | Create | |
|---|---|---|
| Tickets | ● | ● |
| Assets | ● | ● |
| Finance | ● | ● |
Assignment and visibility follow org structure.
Frequently asked questions
Ready to try Core?
Start a free trial or talk to us about rolling out Team Management with your team.