Template Console Guide

This page explains the Template entity in the Namirasoft Password Console. Templates define the structure and rules used when generating passwords for new entries, allowing users to create consistent, secure passwords that align with their personal or organizational requirements.

Templates are reusable and can be applied whenever a password needs to be generated, including through the browser extension during sign-up or password change flows.

Overview of Template Fields and Options

Below is a detailed explanation of each field and option available when creating or managing a Template. Understanding these definitions helps you design password rules that meet your security expectations while remaining easy to reuse across entries.

• ID (string): This field represents the unique identifier assigned to the template. It is generated automatically and is used internally to reference the template across the system.

• User ID (Namirasoft Account’s ID): This field represents the Namirasoft Account identifier of the user who owns the template. It associates the template with its creator and determines access and visibility within the console.

• Name (String): This field represents a human-readable label used to identify the template. The name helps distinguish templates based on their intended use, such as personal accounts, work systems, or high-security environments.

• Type (Enum): This field represents the method used to construct the password. The selected type determines which additional fields are applicable.

• • Character Set: Passwords are generated using selected character categories from the available options.

• • Pattern: Passwords follow a user-defined structure.

• Length (Integer): This field represents the total number of characters that will be included in generated passwords. It defines the overall password size and directly influences password strength.

• Uppercase (Yes/ No): This option represents the inclusion of uppercase letters such as A through Z.

• Lowercase (Yes/ No): This option represents the inclusion of lowercase letters such as a through z.

• Digit (Yes/ No): This option represents the inclusion of numeric characters, typically digits from 0 to 9.

• Space (Yes/ No): This is a checkbox that represents the inclusion of space characters, which may be required for specific password policies.

• Underline (Yes/ No): This option represents the inclusion of the underscore character ( _ ).

• Minus (Yes/ No): This option represents the inclusion of the hyphen character (-) in generated passwords.

• Special (Yes/ No): This option represents the inclusion of common special characters, such as !, @, #, $, and similar symbols.

• Brackets (Yes/ No): This option represents the inclusion of bracket characters, including parentheses, square brackets, curly braces, and angle brackets.

• Latin (Yes/ No): This option represents the inclusion of extended Latin characters, such as accented letters used in certain languages.

• Pattern: The Pattern field represents a rule-based password structure that defines exactly how a generated password should be formed. Instead of selecting character groups through checkboxes, a pattern allows users to explicitly control the position, type, and exclusion of characters in each part of the password.

Each symbol in the pattern corresponds to a predefined character rule. The password generator evaluates the pattern from left to right and replaces each rule token with a randomly selected character from its defined character set.

Patterns follow a strict syntax, and only supported tokens are interpreted as rules. Any character not matching a supported token is treated as a literal character and included as-is in the generated password.

Supported Pattern Tokens and Rules

Each token below represents a character rule. Uppercase tokens indicate exclusion rules, meaning the character will be selected from all available characters except the defined set.

General Tokens

• \.
  Represents any available character from all supported character sets.

Alphabet Rules

• \l
  Represents lowercase letters (a–z)

• \L
  Represents any character except lowercase letters

• \u
  Represents uppercase letters (A–Z)

• \U
  Represents any character except uppercase letters

• \c
  Represents alphabetic characters, including lowercase and uppercase letters

• \C
  Represents any character except alphabetic characters

Word and Digit Rules

• \d
  Represents digits (0–9)

• \D
  Represents any character except digits

• \w
  Represents word characters, including lowercase letters, uppercase letters, and digits

• \W
  Represents any character except word characters

Special Character Rules

• \s
  Represents special characters, such as punctuation and symbols

• \S
  Represents any character except special characters

Bracket Rules

• \b
  Represents bracket characters, including [ ] { } ( ) < >

• \B
  Represents any character except bracket characters

Latin-1 Supplement Rules

• \a
  Represents Latin-1 Supplement characters, such as accented letters (À, É, Ô, Ü, …)

• \A
  Represents any character except Latin-1 Supplement characters

Literal Characters in Patterns

Any character in the pattern that does not match a supported rule token is treated as a fixed literal. This allows users to embed required characters, separators, or symbols directly into the password structure.

Example: Admin-\u\u\d\d

This pattern always starts with Admin-, followed by two uppercase letters and two digits.

• Randomly Permute Pattern (Yes/ No): This option represents whether the characters generated from the pattern should be shuffled randomly. When enabled, the structure is preserved while the character order varies.

• Preview (Read-only): The Preview field displays sample passwords generated in real time based on the defined pattern. This allows users to verify that the pattern produces the expected structure and character diversity before using the template.

• Description (String): This field represents optional contextual information about the template. It is commonly used to explain the purpose, intended usage, or security level of the template.

• Created At (DateTime): It represents the date and time when the template was originally created. It provides historical context and does not change.

• Updated At (DateTime): It represents the most recent date and time the template was modified. It updates whenever any template configuration is changed.