Configure organization identity & settings

Set the organization-wide defaults that shape the whole platform — branding and localization, record ID formatting, the email sender, and governance policies.

System settings hold the organization-wide configuration that shapes how the platform looks and behaves for everyone — the defaults that apply across all projects unless something more specific overrides them. Getting them right once establishes a consistent foundation, so this is worth doing deliberately and early. For the reference, see System settings.

Set identity, branding & localization

These are the settings that make the workspace recognizably yours and present information the way your users expect.

Before you start Open Administration and go to System settings. You'll need administrator access.

  1. Set the organization name, upload an organization logo, and choose a primary brand color so the workspace reflects your organization.
  2. Set the localization choices — language, timezone, and date and time formats — that determine how information is presented.

Result A workspace that looks like yours and reads correctly for your users. See System settings.

Shape record identifiers

Identifier formatting controls the shape of the IDs every record carries — worth setting before records start being created.

  1. Set a global ID prefix for the identifiers records carry.
  2. Choose whether to include the item type key in identifiers, so your numbering scheme is consistent and meaningful rather than arbitrary.

Result Every record carries an ID that fits a deliberate, organization-wide scheme.

Set the email sender and governance policies

These settings govern who notifications appear to come from and the broad rules the organization operates under.

  1. Configure the from name and from email the platform's notifications are sent under, so messages arrive looking like they come from your organization.
  2. Set the data retention policies that govern how long records are kept.
  3. Set the security policies that govern how access is protected.

Result Notifications carry your identity, and the organization's retention and security rules are in force everywhere.

Note Because these apply across everything, getting them right once saves a great deal of correction later. Identity and ID formatting in particular are disruptive to change after records exist — set the numbering scheme deliberately up front rather than reshaping it once IDs are in circulation.

Where to go next

The sender configured here is the identity behind the events and templates in Email notifications. How those messages reach each person is described in Email & preferences.

Was this helpful?