Your First Realm

Realms are isolated containers for users and accounts. You could also think of them as projects. Each realm is fully separate and can have distinct settings, domains, etc.

Often one realm is used per app or project. However, if you’d like multiple apps to share logins (aka SSO), use a single realm.

Since this is your first realm, we’ll assume this is a development realm. You can create another realm later when you move your app into production.

To start, login and, if you haven’t already, add AuthRocket to your account. Select the Trial Plan to get going quickly.

In AuthRocket, you’ll likely be directly at the Realms list, showing no realms yet. Click on the ‘Add a realm’ button. If for some reason you’re not there, you can also click on Realms at the top and select ‘Add realm’.


Let’s go through each of the fields.

App name

This is the name of your app or project. Don’t worry, you can change it later if required.

Environment

Select ‘Development’ since you’re in development still. In Production mode, you’d select that. If you decide to re-use a realm for production later, you can always change this.

Why does it matter? In Development mode, AuthRocket relaxes certain rules, such as allowing http:// for many URLs, making it easier to test.

Brand color

Already have a primary color for your brand or project? Select it here. Not sure yet? Leave the default and come back to it later.

Logos

AuthRocket supports two types of logos: one with a wordmark and one without. If you don’t have logos ready-to-go, feel free to leave these for later too.

SVG, PNG, and JPG are all supported. We recommend SVG if you have one available.

Signups

Open allows anyone to signup. When you launch, you’ll probably want this. For development realms, you may want this as well.

Request invitation replaces the signup form with a request invitation form. Invitations show up inside AuthRocket, where you can simply click ‘Invite’. This is great for pre-launch where you want to start collecting email addresses from interested people, while not yet opening up to the whole world.

Closed disables both signup and requesting an invitation, but you may still manually invite a friend or colleague.

Multi-user (team) accounts

Most B2C (consumer) apps will want Single-user. In Single-user mode, each user belongs to exactly one account—their own.

Most B2B (business) apps will want Multi-user. Multi-user mode allows multiple users to belong to a single account (aka team accounts). It also enables account admins to invite other users to join their account. Lastly, it allow users to have or belong to many accounts.

If you’re not sure, make your best guess, although you can change later.

App or login URL

This is the URL to your app. In development mode, it’s very likely http://localhost:[port]/. You’ll need to substitute the proper port number that matches your app framework (commonly 3000, 5000, or 8000). In production, this will be your app’s URL (using https).

Depending on how you setup integration, this may need to end with /login or similar (eg: http://localhost:3000/login), instead of just /. Like everything else, it’s easily changable later, so if you’re not sure, you can leave the path as just / for now.


Click ‘Add’ and you’re on your way!

Next, go to Integration at the top. You should be asked for what languages and frameworks you’re using on both the frontend and backend.

Select as many as apply—we use this to help customize the Integration section’s instructions specifically for you.

After saving, go to Using LoginRocket if not there already. The language/framework selector is in the upper right if you need it.

The integration details should include links to the matching Integration Guides. Head there next!