Skip to content
Aeropage Documentation
Users, Portals & Members

Managing User Groups & Portals

Authentication Types

There are different ways to determine who a person is, some are more strict and secure while others simply rely on asking them to confirm some information only they would know. You can control the authentication options for your project from the private root.

The authentication settings apply to all portals in the project.


When someone enters their email during login - if it matches a user record they will receive a link via email. Clicking the link will log them in. This authentication method is a bit controversial, some people love it and some hate it. But from a management and security perspective it's much, much better than having a username and password combination.

This method uses google login and is extremely convenient for users on google chrome.

These methods avoid the storage or management of passwords, which is beneficial for security and compliance reasons.

How Membership (Authorization) Works

The presence of a record in a specific table / view defines membership in a group, and authorizes an account to view pages within a portal branch. If a record is found they can proceed, and the pages they visit in the branch will be able to access and display the data from the user’s record. If not they will be shown a message, or allowed to add themselves (signup) depending on the configuration.
Untitled 1.png

Create Portals & User Groups

Each user group has a corresponding portal, so they are both created in the same way. Just click the plus icon at the private root. This will add a new user group and portal page.

Connect the Airtable view with user records to your projec first.

Choose the data source with your user records.
Untitled 2.png

Configure the portal as desired.
Untitled 3.png

Login Field
By default, the system will find a field that contains email addresses and use it to check for a corresponding value. You can customize this, to use a different email field - or if you’re using a passcode login to define the field that contains the passcode values.

If someone is authenticated (logged in) but not authorized (no user record is found in the group) you can give them the option to add a user record themselves. This adds a record if none is found - with the authenticated email address, allowing anyone to add themselves as a member of a group or ‘sign up’.

Passcode Login*
Switching on passcode login for a specific portal will actually remove any real authentication - people only need to provide any value that matches a value in the record. So for example you can give each user a number and have them enter the number.

Passcode login will skip full authentication, use with caution.

Login Screens

You may be interested in customizing your portals or login and logout flows. You can customize the login screen by clicking the portal and then opening the login screen editing mode.

Untitled 4.png

Login (component)
You can add a login component anywhere in a page to allow people to login even outside of portals, though only the default fields will be accessible.

Logout (action)
You can add a logout action to any component, so that clicking will log the user out from their account and all user groups.

Multiple User Groups / Portals

You can add as many user portals as you need, each with a different membership - either from different tables, or by filtering the same table with different views to include or exclude users from groups.

Untitled 5.png

To allow users to navigate to the portals, just create a page with links to each portal.

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.