Skip to content

Portals

A Portal is a standalone web application built on top of your data model and automation. Each portal gets its own URL, its own navigation, its own branding, and its own home page. A single application can have multiple portals - for example, a customer-facing portal and an internal operations portal, each showing different pages to different users.


Navigate to User Interface - Portals to see all portals in the current application:

ColumnDescription
Portal NameHuman-readable name
Portal IDUnique identifier
Module NameWhich module the portal belongs to
Created ByThe user who created it
Modified OnLast modification timestamp

Use + Add Portal to create a new portal, and the row checkboxes plus Delete to remove portals in bulk.


Clicking + Add Portal opens the Add Portal panel:

FieldDescription
Portal NameHuman-readable name
Portal IDAuto-generated from the name
Portal ModuleWhich module this portal belongs to
SubdomainThe subdomain that determines this portal’s URL (see Portal URLs below)
Portal TitleText shown on the portal’s login page
NavigationThe Navigation to use. Leave empty to have a new navigation created automatically alongside the portal.
Open Page InHow pages open when a user navigates: Tab (each navigation opens in the same tab, replacing the current page) or Window (each navigation opens a new window or tab)
Home Page TypeWhat the portal’s landing page is - Page, Entity, or Module (see Home page types below)
Use Custom LoaderWhen checked, reveals the Custom Loader upload - replace the default loading animation with your own file
LogoDisplayed on the login page and in the expanded navigation sidebar
Logo SmallDisplayed in the collapsed navigation sidebar (icon-only state)

Every portal is served at its own subdomain within your workspace:

<subdomain>.<workspace>.anybuild.dev

The main portal uses the workspace root. Additional portals each use the Subdomain set during creation to get their own address - for example, a portal with subdomain customers would be available at customers.<workspace>.anybuild.dev.


The Home Page Type setting controls what a user sees when they first open the portal (or navigate to its root). Three options are available:

Points the home page to a specific Portal Page. Select the target page from the Home Page dropdown.

Renders a built-in entity view as the home page. After selecting Entity, two further settings appear:

FieldDescription
EntityThe entity to render
Widget TypeList - shows the entity’s record list; Details - shows a single record’s detail view

When Details is selected, a Mappings section appears to specify which instance to open - map the record’s identifiers (System ID, System Version) from a fixed value or context.

Opens the module’s data entry view as the home page. Select the target Module from the dropdown.


Click a portal to open its detail view. Top right actions: Open Portal (opens the portal in a new tab), Security Rules, Clone.

Two tabs sit below the header:

  • Details - the Portal Info card showing Portal Name, Portal ID, Portal Module, Portal Title, and Subdomain. Click Edit to update any of these settings.
  • Theme - theming options for the portal’s visual appearance.

Security Rules (top right of the detail view) controls who can access this portal. Each rule sets whether a user or group can open the portal at all.

FieldDescription
Rule NameHuman-readable name for the rule
Access LevelAllow - the matched users can access the portal; Forbid - they cannot
All UsersWhen checked, the rule applies to all users. An All Users Type option appears: Signed-In Users Only (authenticated users) or Signed-In and Anonymous Users (includes unauthenticated visitors)
Security DimensionsWhen All Users is unchecked: one or more User or Role entries the rule applies to, with + Add more for additional entries

A portal is the container - its content comes from the Navigation that structures the menu, and the Portal Pages and Portal Components that make up its screens.