Organizations and modules
Each organization lives on its own subdomain and in its own database schema. Switch any of the field modules on or off per tenant without a release.
Admin console · one deployment, every organization
Run the whole organization from one secure desk.
Modules, people, devices, approvals, and sign-in policy for your organization, served on your own address from a console platform operators keep running for everyone.
What admins control
Everything the field relies on, set in one place.
Change a module, a role, or a policy here and the field app reflects it on the next sync.
Users and devices
Tenant admins invite users with a code, see which devices they sign in from, and remove access instantly when someone leaves.
Device approval
New devices wait for approval. A platform-wide catalog of known models flags installations that do not match.
Schedule approval hierarchy
Model your reporting lines once. Schedule plans route through them automatically before they reach the field.
Sign-in providers
Platform admins configure the providers; each tenant chooses its access strategy, including login-location checks and mock-location detection.
Branding and appearance
The console and the field app carry your identity: logo, accent, and theme variants are set by the tenant admin.
Fleet analytics
Platform operators see counts for every organization over 7, 30, or 90 days, with the previous window for comparison.
Support inbox
Bug reports, feedback, and suggestions submitted from the field.
Three roles, three hosts
Each role gets its own door.
The host picks the organization. Sessions are bound to that host, so an admin signed in to one organization is never signed in to another.
Platform operator
imc.ikonsalesforce.com
Creates organizations, picks their modules, configures sign-in providers and the device catalog, and watches fleet activity across every tenant.
- Tenants
- Device catalog
- Platform users
- Authentication
- Fleet analytics
Organization admin
{your-org}.ikonsalesforce.com
Runs one organization: invites users, approves devices, sets the schedule approval hierarchy, and brands the console and app.
- Users
- Devices
- Device approval
- Approval hierarchy
- Branding
Field user
app.ikonsalesforce.com
Uses the field app on a phone, tablet, or in the browser. Joins with an invite code and sees only the modules switched on for the organization.
- Field app
- Offline sync
- Invite links
How tenancy works
Your organization, your address, your data.
New organizations are live in minutes, with a subdomain, an isolated database schema, and the modules you choose.
- A subdomain is assigned at creation and can be changed; reserved names like app, api, and admin are rejected.
- Bring a custom web domain and point it at the same console; it resolves to your organization the same way.
- All data for the organization lives in its own schema. Reports, users, and devices never share tables with another tenant.
- Field users are not tied to a host. Their invite code identifies the organization, so one app install works for everyone.
Hosts
- northwind.ikonsalesforce.com
- Northwind Pharma admin
- caspian.ikonsalesforce.com
- Caspian Health admin
- admin.northwind-pharma.com
- Custom domain → Northwind
- app.ikonsalesforce.com
- Field app, every organization
- imc.ikonsalesforce.com
- Platform operators
- api.ikonsalesforce.com
- One API behind all of it
✓ Sessions are host-only cookies. No shared domain cookie, no cross-tenant session.
Security
Isolation enforced at every layer.
Tenant isolation
Each organization's data lives in its own database schema, resolved per request.
Host-scoped sessions
Admin sessions are bound to a single host. A session on one tenant is never sent to another.
Device trust
New installations wait for approval and are matched against a catalog of known models.
Role-based access
Platform admin, organization admin, and field roles with separate consoles and permissions.
Login location checks
Geolocation-aware sign-in and mock-location detection, configured per organization.
Origin-checked operators
Platform operator tokens are only accepted from the platform console's own origin.
Give your managers a console they will actually open.
We will stand up a demo organization on its own subdomain and show you the admin console end to end.