System Admin
Configure the company, users, workflows, custom fields, printing, communications and integrations. Administrative changes affect other users and should be tested in staging before production deployment.
Start with your activity
Configure the company, users, workflows, custom fields, printing, communications and integrations. Administrative changes affect other users and should be tested in staging before production deployment.
Customization
Use Customize Form and Custom Field for supported record extensions. Choose an appropriate field type, label, identifier and placement. Test required, unique and link behavior in staging, and check impact on reports, imports and APIs.
↗10 documented pagesDocuments & Printing
Choose the print format and letterhead, review the preview, and export the document when permitted. Maintain the company logo and contact details. Never alter business values in a print template to disguise a transaction error.
↗13 documented pagesEmail & Notifications
Maintain sending and receiving configuration, templates and notification rules. Check sender identity and delivery before enabling automatic notifications. Never place mailbox passwords or service keys in documentation or public fields.
↗21 documented pagesUsers & Permissions
Create users and assign the roles required for their duties. System users and website users have different access. Test both allowed and denied record access; creating a role is not a reason to grant unrestricted administrator rights.
↗22 documented pagesIntegrations & API Docs
Use the API documentation at api.nexcommand.ai, obtain the required authorized credentials and use the deployment-specific service URLs. SaaS tenants and on-premises installations must retain their own endpoints and access boundaries.
↗24 documented pagesMonitoring & Backups
Review the available system health, logs, scheduled jobs and backup controls. A backup is useful only when its restore procedure and required recovery keys are known and tested.
↗23 documented pagesNavigation Setup
Keep the 14-app structure and module landing dashboards aligned with permitted ERP routes. Search and direct links complement the menu. Do not expose a route solely to avoid fixing an underlying permission issue.
↗7 documented pagesCompany Setup
Maintain company identity, accounting defaults, addresses and organization structure. Review the company selected on every transaction. Company print setup uses the location directory and does not replace a supplier or customer address.
↗41 documented pagesPlatform Settings
Review platform defaults and dependencies within the administrator’s authority. Record the reason and tested impact of changes. Authentication, session settings and security-sensitive configuration need a controlled change process.
↗7 documented pagesShared Reference Data
Maintain approved reference lists and directory relationships. For locations, select country, region and city from the directory. For classifications, preserve the parent-child hierarchy and code identifiers.
↗21 documented pagesWebsites & Portals
Maintain published pages, web forms and portal configuration. Keep public content separate from role-restricted ERP data. Test logged-out access and the correct linked stakeholder account before release.
↗14 documented pagesWorkflow & Automation
Configure workflow states, transitions, assignments and notifications against the correct record type. Define which role may act at each step and test the complete lifecycle in staging.
↗Task tutorials
Add custom fields to customer records
A Table field needs a suitable child record type. Adding a form field does not automatically add it to every report or API client.
↗TutorialConfigure a company logo and print address
The address stored for a Company is separate from a Supplier address. If an upload fails, check File permission and the parent record access; do not make private attachments public to bypass an error.
↗TutorialConfigure users and stakeholder access
Creating a login does not automatically authorize customer, supplier or employee data. Use the corresponding verified party relationship.
↗TutorialUse the API documentation
The documentation describes the supported interfaces. A client deployment uses its own URLs and credentials, not NexCommand production credentials.
↗TutorialConfigure a workflow and notification
A displayed status field can be read-only or controlled by a workflow. A notification rule needs a working outgoing email account to deliver messages.
↗TutorialPrepare a backup and recovery procedure
A successful backup command is not a restore test. Do not overwrite live business records with staging data during a software release.
↗