Security Overview
Security in qRaptor has two layers, and it helps to separate them:
- What the platform enforces for you — access, tool permissions, data rules, approvals and audit, enforced beneath the model for humans and agents alike. You don’t build this; it ships with the platform. See Platform governance.
- What you define for your own apps — the users, roles, permissions and login experience for the apps and agents you build. That’s this section.
This section covers the second layer. It has five tabs: Users, Roles, Permissions, Data Governance, and Auth Settings.
All five live in the project sidebar under Security.
Looking for who can manage your qRaptor project or its teams? That’s Roles & permissions — a different, fixed set of roles (Owner/Admin/Developer/Viewer) for people who build in qRaptor Studio. Everything under Security instead manages the end users of your generated apps, via a separate org (Keycloak-backed) role system you define yourself.
- Owner or Admin — every tab requires project admin access to edit; everyone else sees the same controls, disabled rather than hidden.
Tabs
| Tab | What it covers |
|---|---|
| Users → | Create, edit, disable, and remove end users of your generated apps |
| Roles → | Define the custom roles your apps’ users can be assigned |
| Permissions → | Control which pages each role can access |
| Data Governance → | Row-level filters and column masking per role |
| Auth Settings → | Sign-in policy, session, email verification, login branding, custom CSS, and SSO |