Your portal is made up of pages:
On a page, you can display apps and data from your project (displaying data is accomplished with a database connection):
In this lesson, you'll learn how to:
- Create and edit pages
- Add apps
- Use conditional logic to display a portal page only under specific circumstances.
This lesson also provides an introduction to database connections, which is explained in detail in its own lesson.
Create a new page
From within the details view of your portal, click "New page":
Give your page a name and choose an icon. Both of these will be used in portal:
The order of your pages here determines the order of pages in the portal:
Edit your page
From within the details view of your portal, click "edit" on a page to edit and build that page:
This is the portal page editor:
From here, you can:
- Add apps
- Add database connections
- Edit portal name and icon
- Add conditional logic that determines whether this page is displayed
Conditionally display page
By default, any page you add to your portal will be displayed to all users in that portal. If you want, you can add conditional logic to your page and have it displayed to users only under certain circumstances.
How it works
- Click the conditionally display toggle at the top of the portal page editor;
- Select a table from your database and then create a filter that will look for a specific record in that table;
- Use the expression editor to create a logical condition that will be applied to the specific record from Step 2. If this condition is satisfied, the page will be displayed in the portal.
If you're going to conditionally display a portal page, you'll likely want to create a condition that's unique to a particular user or group of users. To do this, you will need to use the portal client id or portal group id variable in your database.
Intro to portal apps
There are two ways to add apps to your portal pages: (1) standalone; and (2) attached to a database connection:
Standalone apps are detached from any data, which doesn't mean they can't use data from your project, it just means that portal users can't use data as easily as they can with apps attached to a database connection (see below).
Adding an app as "standalone" is best for apps that create, instead of consume, records of data.
Learn how to add a standalone app.
Attached to database connection
This is the easiest way to allow portal users to use data in their app. If you attach an app to a database connection, the portal user is able to simply click on a record of data and then select the app (the app will then use that record's data):
Learn how to attach an app to a database connection.
Attach app to a database connection
This is the easiest way to allow your portal users to use your apps with their data. In practice, the portal user will simply need to click on a database record and then select the app from the dropdown in the "toolbar":
You must first have an app that:
Next, you'll need to add the database to which this app is attached as a database connection in your portal (check out our lesson on database connections).
Finally, simply click the 'Include app toolbar' toggle for your database connection:
Add standalone app
To add a standalone app, just select the app and click "add" in the portal page editor:
Intro to database connections
A database connection allows you to expose part of your project's database to your portal users.
You have total control over how data is displayed, including the visual layout, the permissions the portal user has, and what data they get to see. Learn how to create a database connection.