Set your organization identity

Define who your organization is at the tenant level — its identifier, primary domain, logo, and status — and handle the primary domain with the care its ties to authentication demand.

The Organization area holds your organization’s core identity at the tenant level — the settings that define who the organization is within TraceUnified, as distinct from how any one project is configured. This guide sets them, and flags the one setting that reaches beyond branding into authentication. For the concepts, see Organization.

Set your core identity

These are the defining attributes of the organization as a whole.

Before you start In the Identity Portal, go to Organization. You'll need administrator access.

  1. Set your organization's defining attributes — its organization ID, primary domain, logo, and status.
  2. Give the primary domain particular attention: beyond branding, it's tied to how users are recognized as belonging to your organization and it underpins access and single sign-on.

Result A clearly defined organization identity at the tenant level. See Organization.

Mind the ripple of a domain change

Most of these settings change rarely; the primary domain is the one to change deliberately.

  1. Treat a change to the primary domain with care — because it underpins authentication, the change ripples through access and SSO.
  2. Coordinate any such change with your single sign-on configuration, so recognition and sign-in stay aligned.

Result Identity changes that don't quietly break authentication. See SSO Configuration.

Note These settings live in the Identity Portal rather than in-product Administration because they describe the organization as a security and identity entity, not as a workspace — the kind of thing an IT or security owner manages. They change rarely, but when they do the change reaches authentication and access, which is exactly why they're governed in the control plane.

Where to go next

For the admins authorized to manage this, see User Management. For the single sign-on tied to your primary domain, see SSO Configuration; to serve the portal under your own address, see Custom Domain.

Was this helpful?