Skip to main content

Users properties

The Users properties screen carries the per-user flags Nomasx-1 uses to interpret usage data. One line per (Application, User). Each row is the place to mark an account as technical, generic, linked to another login, privileged, or attached to a previous account.

These flags are read by OUT — Users / Roles, the Licenses reports and several account-hygiene views — they let the analysis distinguish a real human from a batch service account or a shared login.

At a glance​

Nomasx-1 · Settings · Security · Users propertiesAPPUSERTECHNICALGENERICCOUNTPRIVILEGEDLINKEDLINKED USER12SVC_BATCHYN—NN—12SHARED01NY12NN—12J.DOENN—NYJDOE

Goal of the view​

Tag each user account so downstream views can filter intelligently:

  • Technical accounts — batch / service users. Excluded from headcount-based licence calculations.
  • Generic accounts — shared logins. Generic count lets you state how many real people are behind it.
  • Privileged accounts — flagged for special audit attention.
  • Linked / Previous accounts — duplicate or successor relationships. Linked User and Previous User hold the reference to the primary login.

Columns​

ColumnSourceWhat it tells you
Application IDUSRP_APPS_ID — application.The application.
User IDUSRP_ID — user identifier.The account being tagged.
TechnicalUSRP_TECHNICAL — Y / N.Marks the account as a service / batch user.
GenericUSRP_GENERIC — Y / N.Marks the account as shared by several people.
Generic countUSRP_GENERIC_COUNT — number.How many real people share the generic account.
PrivilegedUSRP_PRIVILEGED — Y / N.Marks the account as carrying elevated privileges.
LinkedUSRP_IS_LINKED — Y / N.Whether the account is declared as duplicate of another.
Linked UserUSRP_ID_LINKED — login.If linked, the primary login it points to.
PreviousUSRP_IS_PREVIOUS — Y / N.Whether the account is the successor of a previously used login.
Previous UserUSRP_ID_PREVIOUS — login.If marked, the previous login.

Edit dialog​

Click Add to declare a flag set on an account, or double-click a row to edit. The form is two-column and groups the flags by kind.

Edit user properties — SVC_BATCHApplication12 — JDE ProductionUser IDSVC_BATCHPrivilegedTechnical✓GenericGeneric count—LinkedLinked user—PreviousPrevious user—CancelSave
FieldWhat to enter
ApplicationDrop-down on add, read-only on edit.
User IDLookup against the user catalog, scoped to the selected application. Read-only on edit.
PrivilegedTick when the account carries elevated privileges.
TechnicalTick when the account is a service / batch user.
GenericTick when the account is a shared login.
Generic countActive when Generic is ticked. Number of real people behind the login.
LinkedTick when the account is a duplicate of another login.
Linked userLookup of the primary login the row points to. Required when Linked is ticked.
PreviousTick when the account is the successor of a previous login.
Previous userLookup of the previous login. Required when Previous is ticked.

Tips & best practices​

  • Tag technical and generic accounts early. Every untagged technical user pollutes the licence headcount.
  • Use Linked for duplicate pairs the Duplicate users screen surfaced as known-good. Declared once, removed from the audit noise.
  • Privileged should be sparing. Setting Privileged = Y is a deliberate audit signal — limit it to accounts that truly carry elevated rights.