Platform & Configuration
System Administration
System Administration is where an organization defines itself to the platform: its profile and business rules, its users and permission groups, its languages and terminology, its reference data, and the license that decides which modules run. Every other module reads this configuration — set once, enforced everywhere.
Reach begins atThe user account
The operating model
A platform that runs HR, supply chain, finance, and project work under one roof needs one place where the organization itself is configured. Administration holds the enterprise profile — name, logo, business hours, default currency and language — alongside the disclaimer users must accept (with each acceptance recorded), organization-wide settings, and the rules that decide who is notified about what.
Access is administered the way the platform is built: by position. Permission groups bundle application and privilege grants, are scoped by what the organization’s license allows, and are bound to positions in the org chart rather than named individuals. When a seat changes hands, its access moves with it — administration maintains the bundles; the org chart decides who currently holds them.
The same surface carries language and meaning. A two-tier localization model translates per-module UI text and lets an organization relabel screens in its own terminology, while categorized lookups give every module its statuses and types from one governed list. Underneath it all sits the license: an encrypted file, validated on upload, that gates which applications exist for the organization at all.
The subject
The user account
- Permission groups
- Licensed modules
- Reference data
- Localization
What this account may actually do
Activate
Upload and validate the organization’s encrypted license; the modules it names become available.
Profile
Record the enterprise profile — name, logo, business hours, currency, language — and publish the disclaimer users must accept.
Model
Build the organization: units, positions, and the people who hold them.
Grant
Bind permission groups to positions so application access follows the seat, not the person.
Localize
Register working languages, translate UI text, and maintain the lookups every screen shares.
Operate
Every module now runs under the license, permissions, languages, and reference data defined here.
Everything inside Admin
5 capabilities
- Enterprise Setup
Where does an organization define its profile, working rules, and legal notices? - Users & Permission Groups
How do we control who can use which applications and act on which records? - Languages & Localization
Can each organization run the platform in its own languages — and its own terminology? - Lookups & Reference Data
Where do the shared code lists behind every module’s statuses and types live? - Licensing & Module Activation
How are modules activated for an organization — and what happens when a license changes?
Connected through one operating model
Admin does not stand alone.
Records cross module boundaries without being re-entered — these are the relationships continON actually maintains.
- Getting Started
The enterprise profile is one of the first steps a new organization completes. - Builders
Report and dashboard visibility attaches to the same positions and partners. - Document Management
File and folder rights use the same grant targets — positions, employees, partners. - Human Capital Management
Employee records are where account provisioning begins.
See Admin on your own operations.
A guided walkthrough on a sanitized demo tenant — this module, the shared platform, and a connected workflow end to end.