Getting Started
Navigating Antly
Find the launchpad, side menu, Sites home, object settings, and global administration areas.
Navigating Antly
Navigating Antly covers how staff move through launchpad, main menus, Sites home, module apps, object lists, global settings, profile, and search. Use this page when you are setting up the product surface, reviewing a rollout, or troubleshooting why users see a different result from an administrator.
What this surface is
- Primary purpose: how staff move through launchpad, main menus, Sites home, module apps, object lists, global settings, profile, and search.
- Where users start: Launchpad opens at
/launchpad; the staff home page opens at/sites/home; settings opens at/global-settings. - Where administrators configure it: Object lists use
/objects/:objectName/list; configurable pages use/sites/:page; personal profile routes start at/profile/my-profile. - Runtime/detail surface: Navigation is filtered by enabled tenant apps, user permissions, menu configuration, and saved launchpad tiles.
- Platform connections: Navigation connects tenant apps, user menus, pages, objects, roles, PWA shortcuts, and global settings.
Where it lives
| Area | Path or surface | Use it for |
|---|---|---|
| User surface | Launchpad opens at /launchpad; the staff home page opens at /sites/home; settings opens at /global-settings. | Day-to-day work and review. |
| Configuration | Object lists use /objects/:objectName/list; configurable pages use /sites/:page; personal profile routes start at /profile/my-profile. | Setup, permissions, routing, labels, and behaviour. |
| Runtime/detail | Navigation is filtered by enabled tenant apps, user permissions, menu configuration, and saved launchpad tiles. | Testing the live experience users actually see. |
Configure it
- Confirm the audience for this surface and whether they are staff users, portal users, customers, public visitors, or administrators.
- Open the owning product route: Launchpad opens at
/launchpad; the staff home page opens at/sites/home; settings opens at/global-settings. - Review the configuration route and permissions before changing live behaviour: Object lists use
/objects/:objectName/list; configurable pages use/sites/:page; personal profile routes start at/profile/my-profile. - Define the primary records, fields, statuses, owners, and notifications involved in this workflow.
- Configure Launchpad, Sites home, and Global settings first because they shape the rest of the rollout.
- Add Object list and Module app only after the core path works with sample data.
- Test the runtime surface as a restricted user, not only as a superadmin: Navigation is filtered by enabled tenant apps, user permissions, menu configuration, and saved launchpad tiles.
- Check downstream connections after saving: Navigation connects tenant apps, user menus, pages, objects, roles, PWA shortcuts, and global settings.
- Record the owner, rollout date, and support path for the configuration.
- Review the first week of activity and remove any option that users do not understand or need.
Configuration options
| Option | Use when | Notes |
|---|---|---|
| Launchpad | Pick an app or shortcut | Route: /launchpad. |
| Sites home | Staff landing page | Route: /sites/home. |
| Global settings | Tenant configuration | Route: /global-settings. |
| Object list | Work with custom records | Route: /objects/:objectName/list. |
| Module app | Work inside an enabled ERP app | Open from launchpad. |
| Profile | Manage personal details and preferences | Route: /profile/my-profile/my-profile. |
Operating notes
- Keep labels aligned with the words users see in the product, especially Launchpad and Sites home.
- Permissions still matter even when a menu, page, or link is visible.
- If users see empty data, check role filters, enabled apps, ownership rules, and saved filters before editing records.
- If a change affects customers or public visitors, test from a logged-out or customer account as appropriate.
- Use reports or logs to confirm the change produced the expected operational result.
- Capture configuration decisions in rollout notes so support teams know what changed.
- Do not reuse one option for unrelated processes just because it is already configured.
- Review linked notifications, workflows, dashboards, and reports after changing this surface.
- Prefer narrow changes that can be tested with sample data before a tenant-wide rollout.
- When troubleshooting, start at the route users open, then inspect configuration, permissions, and logs in that order.
- Keep retired settings hidden or archived so users do not choose outdated paths.
- Assign an owner for ongoing review; unattended configuration becomes stale quickly.
For developers
Use these pages when the surface is read or changed by code, scripts, embeds, widgets, API clients, webhooks, or realtime listeners.