People who have accounts in your portal are not Afterpattern users, they are your users. They are using the apps and databases that you've built with Afterpattern, but they do not need an Afterpattern account; they just need an account in your portal.
This lesson explains how to manage your users, including:
You must have at least a Professional subscription to Afterpattern to create users, however you can add one test user for free.
To create a test user, click "Add test user" from the portal detail view:
The test user's email is the same as the email address associated with your Afterpattern account.
You can only have one test user per project. If you need to test two portals in the same project, you'll have to delete the test user from one portal before adding it to the other.
After you create the test user, copy the invite link from the user actions dropdown:
Pro tip: Paste the copy invite link into an incognito window. This guarantees there are no lingering cookies that may be associated with previous test user accounts.
There are two ways to add new users:
You always have the ability to manually add new users. You can only use the public auto sign up page if, when you initially created the portal, you toggled this feature on.
You must have at least a Professional subscription to Afterpattern to create users, but you can add a test user for free (see above).
From the portal detail view, click "Add new user":
Next, edit the details for your new user, including the email they will use to log in, a static subscription fee, and their unique portal client id (learn how to use the portal client id to create database connection filters that result in the user viewing only their data):
After you create this new user, send them the "invite link" that allows then to log into your portal for the first time. You can find this link by clicking the actions dropdown for your user:
When you users follows the invite link, they'll land on your portal's log in page with their email pre-populated. All they need to do is create a password:
If your portal has a public auto sign up page, you find the URL for this page under the portal details view:
You can use this URL in a number of ways, including:
The purpose of this URL is to allow anyone with access to it to sign up to your portal.
You can view a list of all users under the portal details view:
For each user, you can view their subscription level, view their last log in date, and open the "Actions" dropdown:
From here, you can edit the user's settings, copy the invite link (used to manually add new users), and remove them from your portal.
If you click "Edit settings" for a user, you open the edit user modal:
This is where you edit user details. Continue reading for a breakdown of everything you can edit.
Every portal user has a unique ID represented by the portal client ID variable. You view the portal client ID for an existing user in the edit user modal.
Learn more about the portal client ID variable.
The portal group ID variable works the same way as the portal client ID, except that it can be shared across multiple users. You can view and edit the portal group ID for an existing user in the edit user modal.
Learn more about the portal group ID variable.
You can manually edit the database connection filters on a per user basis. You do this under the edit user modal.
Database connections give portal users the ability to view and edit data from your database. The database connection filter determines what data is displayed to the user.
Normally, when you edit a database connection filter (assuming the "Changes apply to existing users" toggle is on), the edit will apply to all portal users.
You can require users to pay a subscription fee before signing up.
If you manually add new users, you can add a subscription when you manually create their account.
When you create a portal with a public auto sign up page, you can add a subscription when you first create the portal:
In either case, this subscription fee is "static", meaning it doesn't change over time. Nor is it something your users can progressively opt into (for example, you may want to allow users to sign up for $0.00 and then progressively increase the subscription fee based on their actions — this is a variable subscription fee which you can learn about below).
Work in progress
