Understanding Page Properties
When you click on Pages in the Dev Toolbox and hover over a page, click on the gear icon i.e. Page Settings , you are looking at the properties of the page.
These settings determine:
-
How the page is identified
-
Who can see it
-
Who is allowed to open it
-
Under what URL it lives
-
What happens when the page loads
1. General Properties
a) Page Name
This is where we can see the page name in the Page name textbox used in lists and internal references.
b) Access Control
This property controls who can access the page.
-
Protected - only logged-in users can open the page. Use this access control for internal tools (CRM, dashboards, offers, invoices).
-
Public - anyone can access, even without logging in. Use this for landing pages, public forms, documentation, marketing pages.
c) Assign Permission
Here you can choose which user roles or permission groups can access this page.
Examples:
- API User
- Account User
- Account Admin
- Admin
- System Admin
These roles are system defaults, but you can create your own personalized roles. If you select specific permissions: only those users can see and open the page.
If you leave it empty: all authenticated users (if the page is Protected) can access it.
Why this matters:
This is the foundation of access management. It prevents unauthorized users from seeing sensitive data.
2. Advanced Properties
a) Page Route
The Page Route property defines the URL where your page is accessible.
Autorun automatically generates it based on the Page Name upon creating a new page.
If you name your page “Offers”, the route becomes:
Example:
/offers
Creating main pages works well with the automatically generated route. However, for subpages, you must correct the route manually.
Subpages often need to display information for a specific record, such as the details of a selected offer. To support this, you have to manually adjust the route to use a dynamic URL. A dynamic URL contains a variable segment - usually an ID - written as:
/offers/:id
The :id acts as a placeholder that changes depending on which record the user opens.
All URLs load the same subpage, but with different data:
Example:
/offers/12
/offers/87
/offers/145
Why this matters:
Correct routes ensure:
-
Navigation links work properly,
-
Components receive the right context and record ID,
-
Browser loads the correct detail page,
-
Your data model stays consistent.
If the route is incorrect, your subpage may not load at all or may fail to fetch the right record.
b) On Load
This property is where you choose a function that runs automatically when the page is opened.
Examples:
-
GenerateQuote
-
SetReminderFunction
-
(no function)
These functions depend heavily on the app itself and what you set it up to be. If you choose no function, the page simply loads without running additional logic.
Powerful for automating workflows.
For example, you might want an Offers page to automatically mark expired offers as “Expired” as soon as the page is opened.