NexCommand AINexCom Knowledge Base
Field reference

Permission Inspector

How to use Permission Inspector in Users & Permissions: access, working steps, fields, related records and troubleshooting.

System AdminUpdated 12 October 2026Configuration-aware guidance
Open Permission Inspector ↗Module guide

Purpose and access

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.

This page is a settings page in System Admin → Users & Permissions. Use the link above to open the configured destination; permissions are checked by the destination service.

ERP links open in a new tab. Sign in with your own account; record visibility, actions and approval authority follow your assigned permissions. Screens can differ by company and configuration.

Before you start

Prepare the required information: DocType, User.

Confirm the company, party, dates, units and source references that apply. Select existing links carefully and check for an existing record before creating a duplicate.

Working steps

  1. Open Permission Inspector from System Admin → Users & Permissions, or use ERP Search.
  2. Review the existing configuration before editing.
  3. Complete the editable fields described below. Required fields and validation conditions must be satisfied; read-only values are set by the system or their source records.
  4. Save the record and address validation messages. Reload and verify the saved values and relationships.
  5. Use any additional workflow actions only when the record and your role provide them. Saving this record does not automatically complete a related transaction or external action.

Field reference

These fields come from the installed ERP definition. Hidden fields and password inputs are omitted. Additional conditions, custom scripts and workflow rules can make a field required or read-only in a particular context.

FieldType / behaviorHow to use it
DocTyperef_doctypeLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: DocType

DocumentdocnameDynamic Link
Optional		Select the record identified by the associated document-type field. Verify both the type and the linked record.
UseruserLink
Required		Choose an existing linked record. Check its company and ownership; typing a label alone does not create a new relationship.

Linked record: User

Permission Typepermission_typeSelect
Optional		Choose one of the configured list values. Status fields may be controlled by the record workflow.
Available choices
  • read
  • write
  • create
  • delete
  • submit
  • cancel
  • select
  • amend
  • print
  • email
  • report
  • import
  • export
  • share
OutputoutputCode
Optional · Read-only		Administrator/integration field. Use a validated configuration or supported script and test its impact before deployment.

Troubleshooting

  • Not permitted: verify the account, role and source-document permission. Do not share an administrator login.
  • Missing record or address: inspect the relevant Link or Dynamic Link fields; a matching title alone does not establish a relationship.
  • Cannot save or change status: review required fields, read-only values, document status and the configured approval transition.
  • Unexpected report or portal result: review company/date filters, source-document submission and the approved party or Employee link.
Was this useful?