Ask our Agents

What is this thing, and what will it take?

Name something a big customer asked for, like SCIM, SOC 2 or RBAC. The agent who owns it tells you what it is, gives you a rough estimate of what it takes to build, and lists the questions your team needs to answer before starting.

RBAC

Role-based access control

What it is

Role-based access control decides what each user is allowed to do. Instead of everyone being an admin or a member, users get roles, and each role carries specific permissions. Enterprise customers usually want to define their own roles, and to limit access to parts of the product, such as one region or one project.

Large companies run on least privilege and separation of duties. If your only options are admin and member, their security team will ask you to change that.

What it takes

About 4–8 engineer-weeks to build in-house, or 2–4 using Oso, Permit.io, Cerbos or SpiceDB.

Answer these first

Product: Which roles do customers actually need on day one?
Product: Can customers create custom roles, or only choose from ours?
Engineering: Where do permission checks live today: backend, frontend, background jobs?
Engineering: Do we need access scoped to specific resources, or only global roles?
Security: Who can grant admin, and is that change logged?
Sales: What exact access request is blocking the current deal?

This page works best with JavaScript on. Every answer also has its own address, like /what/scim.

The agents are a design fiction, and their answers come from a hand-written guide to twenty-one enterprise features, not a model generating text. Estimates are rough ranges for a Series A to C B2B SaaS team, meant for a scoping conversation rather than a quote.