Overview
How a new Auth tenant comes into existence — provisioned through Eved, not through the API.
Provisioning a Febasi Auth tenant is done through the Eved platform, not by calling the Auth API directly. You create a project of type Authentication inside a workspace; the wizard collects your tenant code, password policy, token lifetimes, and session limits, then provisions the tenant in the Auth service and returns you to its dashboard.
This topic explains why the path runs through Eved and what you have right after the wizard finishes.
Why Eved is the entry point
A tenant is more than a row in a database — it ships with default roles, a JWT signing context, and a wired-up dashboard. The Eved Auth wizard provisions all of that in one transaction and ties it to a project in your workspace, so you have a single place to administer the tenant later. Calling the bare API would skip the dashboard wiring and require you to seed the same defaults by hand.
For tenant operators, this means the only thing you need to do is sign in to Eved.
If you already have a tenant
Skip this topic and go straight to Registration or Login & sessions.
What's in this topic
Provisioning a tenant
The five steps of the Eved Auth wizard, what each field controls, and what is editable after creation.
Summary
Cheat sheet — the wizard at a glance, defaults, and what to do next.
Related
- Eved → Getting started — sign in, create your workspace, create the project.
- Eved → Auth project — the full wizard walkthrough.
- Concepts → Multi-tenancy — the isolation model your tenant inherits.