Get started
How the Enjab tools fit together and the fastest path to a working tool - login plus on-brand UI.
An Enjab tool is a web app that two Enjab services take care of for you:
- Sign in with Enjab Auth handles who the user is and whether they may use your tool. You never build a login screen or touch a password.
- Enjab UI gives you the look - a themed component registry and a dashboard shell, so every Enjab tool feels like one product.
You build the part in the middle: your tool's actual features. Everything else is provided.
The shape of an Enjab tool
- It lives on an
enjab.aedomain (e.g.yourtool.enjab.ae). Auth refuses any other domain. - The instant a signed-out visitor touches any page, they are redirected to Enjab to sign in. No login button, no login page of your own.
- Once signed in, you key all your own data by the user's stable Enjab id (
sub). - Your dashboard uses the Enjab UI shell, so the sidebar, account block, and the "an Enjab product" byline are consistent with every other tool.
Fastest path
Register the tool (one time)
An Enjab admin adds your tool in auth.enjab.ae/admin and hands
you a ENJAB_CLIENT_ID + ENJAB_CLIENT_SECRET. See
Sign in with Enjab Auth → register for the exact steps.
Wire up login
Drop in the four reference files (lib/enjab-auth.ts, the callback route, the logout
route, and proxy.ts). Set your four environment variables. That is the whole
integration - copy them from Sign in with Enjab Auth.
Add the UI
Install the Enjab UI chrome and theme, then build your screens with the registry components so your tool matches the rest of Enjab. See Enjab UI.
Handing this to an agent
Give your coding agent this site's /llms.txt (or the specific page's raw
markdown) and the task. The pages are written so the agent can do each step end to end.