More results...

Generic selectors
Exact matches only
Search in title
Search in content
Post Type Selectors
Search in posts
Search in pages
docs
betterdocs_faq

Partner/Employer username format

  • Created on July 1, 2026
Updated on July 1, 2026

6 min to read

Table of contents

Overview

The Partner/Employer username format setting allows administrators to define a consistent, automatic pattern for generating login account names for Partner (Employer) entities in Classter. Instead of entering a username manually each time a new Partner/Employer is created, Classter reads this pattern and suggests an account name automatically, ensuring that all Partner/Employer accounts follow a uniform, predictable naming convention.

This setting is configured per institution. Each institution on a shared platform can maintain its own format independently.

 

What This Setting Does

When a new Partner/Employer record is added to Classter, the system reads the format defined in this setting and uses it to build a suggested username for that entity. The username suggestion appears automatically in the account creation form, saving time and reducing the risk of inconsistent naming.

The format is a text pattern composed of placeholder tokens representing specific fields of the Partner/Employer record — such as the entity’s title (company or organisation name) or its internal code. Tokens can be combined with separator characters (such as a dot or underscore) to produce usernames in any style required.

Important points:

  • The system proposes a username — the administrator can accept the suggestion or override it manually.
  • If the suggested username already exists in the system, Classter automatically appends an incrementing number to guarantee uniqueness (for example: globalcorp, globalcorp1, globalcorp2).
  • If this setting is left blank, no suggestion is generated and administrators must type the username manually every time.

 

Where It Is Used

 

Location in Classter

Main Settings > General Settings > Security Settings > Accounts & Roles

The setting is located in the Accounts & Roles section alongside the equivalent username format settings for other user types (Students, Teachers, Employees, and Parents).

 

When It Takes Effect

Every time a new Partner/Employer record is created and assigned a login account in Classter, the system uses this format to suggest the account name.

 

Who Configures It

Institution administrators, as part of initial setup or whenever the institution updates its account naming policy.

 

Business Logic / Behavior

 

Format Tokens

The format pattern is assembled from tokens and optional static separators. The following tokens are available for the Partner/Employer entity:

Understanding the N Parameter

N is a number that controls how many characters are extracted from the selected field:

  • N = 1 takes only the first character (e.g., the first letter of the title).
  • N = 10 takes up to the first ten characters (or the full value if it is shorter than ten characters).
  • A large N value such as 50 or 100 effectively means use the entire field value.
  • The special form (0, ‘ ‘) takes only the first word of the field, stopping at the first space. This is useful for Partners/Employers whose title contains more than one word.

 

Separators

A static separator character — such as a full stop (.) or an underscore (_) — can be placed directly between tokens to structure the username. For example, a dot between a code token and a title token would produce a format like code.title.

 

Uniqueness Rule

If the username generated by the format already exists in the system (because a different Partner/Employer already has the same derived name), Classter automatically appends an incrementing integer to make it unique. For example: globalcorp becomes globalcorp1, then globalcorp2, and so on. Administrators do not need to handle uniqueness manually.

 

K-12 Mode vs. Higher Education Mode

This setting behaves identically in both K-12 mode and Higher Education mode. The label, location, available tokens, and functionality are the same regardless of which mode the institution operates in. No distinction in behavior applies.

 

Examples

 

Example 1 — Full title as username

Format configured as: [SchoolPortal.Title(10)]

A new Partner/Employer is added with the title: Bright Solutions

Suggested username: brightsolu

Explanation: N = 10 means the first ten characters of the title are used. The title Bright Solutions has ten characters before the space is reached.

 

Example 2 — First word of the title only

Format configured as: [SchoolPortal.Title(0,’ ‘)]

A new Partner/Employer is added with the title: North Star Academy Partners

Suggested username: north

Explanation: The (0,’ ‘) parameter stops extraction at the first space, so only the first word of the title is used.

 

Example 3 — Internal code as the username

Format configured as: [SchoolPortal.Code]

A new Partner/Employer is added with the internal code: EMP-0042

Suggested username: EMP-0042

Explanation: This format is useful when Partners/Employers already have an official code in the institution’s records and that code is meaningful as a login name.

 

Example 4 — Code combined with first word of title

Format configured as: [SchoolPortal.Code].[SchoolPortal.Title(0,’ ‘)]

A new Partner/Employer is added with code EMP-0015 and title: Redwood Technology

Suggested username: EMP-0015.redwood

Explanation: The code and the first word of the title are combined with a dot separator.

 

Example 5 — Handling duplicate usernames automatically

Format configured as: [SchoolPortal.Title(10)]

Two different Partners/Employers both have a title starting with Blue Ocean:

  • First Partner/Employer created → suggested username: blueocean
  • Second Partner/Employer created → Classter automatically suggests: blueocean1

No manual action is required from the administrator.

 

When to Use

 

Configure This Setting When

  • Your institution assigns login accounts to Partners/Employers — for example, when employers need to access a partner portal to view student placements, internship progress, or other shared data.
  • You want all Partner/Employer usernames to follow a consistent, recognisable naming convention without requiring manual entry each time.
  • Your institution has a large or growing number of Partners/Employers to onboard and wants to reduce administrative effort.
  • Your institution is setting up Classter for the first time and defining account naming policies for all user types.

 

Leave Blank (or Do Not Configure) When

  • Partner/Employer login accounts are created very rarely and administrators prefer to assign usernames manually on a case-by-case basis.
  • Your institution does not grant system login access to Partners/Employers at all.

 

Notes

 

Prerequisites

Before configuring this setting, ensure the following:

  • The Partner/Employer entity record must have its relevant fields filled in (most importantly, the title/name field) for the format to generate a meaningful username. If required fields are blank, the suggested username may be incomplete or empty.
  • If your institution integrates with an external identity provider (such as Microsoft 365 or Google Workspace), verify that the username format you define here is compatible with that provider’s username rules before saving.
  • For institutions running multiple branches or institutions on the same platform, configure the Append a suffix to the username account setting as well, to avoid username conflicts across institutions.

 

Related Settings

The following settings work in exactly the same way but apply to different user types. All are located at Main Settings > General Settings > Security Settings > Accounts & Roles:

  • Student (Pupil) username format — SchoolPortal_Morfi_Onomatos_Xristi_Mathiti
  • Employee username format — SchoolPortal_Morfi_Onomatos_Xristi
  • Teacher username format — SchoolPortal_Morfi_Onomatos_Xristi_Kathigiti
  • Parent (Guardian) username format — SchoolPortal_Morfi_Onomatos_Xristi_Gonea

Changes to any one of these settings do not affect the others.

The following setting complements the username format in multi-institution environments:

  • Append a suffix to the username account (Main Settings > General Settings > Security Settings > External Sync — SchoolPortal_Onomasia_Kentrou): Adds a fixed suffix to all generated usernames for a given institution. Useful when multiple institutions share the same platform and need to ensure unique usernames across all of them.

The following setting controls the default access role assigned to new Partner/Employer accounts and should be configured alongside the username format:

  • Partner Dashboard Default Role (Main Settings > General Settings > Security Settings > Accounts & Roles — Partner_Dashboard_Default_Role): Defines the default role that every new Partner/Employer account receives when it is created in Classter.

 

Editing the Format

To open the format builder, click the three-dots button next to this setting. A popup form will appear where you can select tokens, add separators, and preview how a sample username would look with your chosen format. Special functions for character conversion (such as converting to lowercase) are available within this popup and are explained in the extra information provided there.

Token

What It Inserts

[SchoolPortal.Title(N)]

Takes the first N characters from the Partner/Employer’s title (the name of the company or organisation).

[SchoolPortal.Code]

Uses the Partner/Employer’s internal identifier code.

[SchoolPortal.CrossCode]

Uses the Partner/Employer’s cross-reference code.

 

Tags
Was this article helpful?