---
title: "Common Registration Info"
description: "The shared fields (Name, Alias, Entity, and Properties like Description, Permissible Purpose, Group, and Keywords) that every registered object has in common."
---

<div style="padding: 14px 16px; border: 0.5px solid #AFA9EC; border-radius: 12px; background: #EEEDFE; margin-bottom: 1.5rem;">
  <div style="display: flex; align-items: center; gap: 7px; margin-bottom: 8px;">
    <svg width="16" height="16" viewBox="0 0 16 16" fill="none">
      <path d="M9 2L4 9h4l-1 5 5-7H8l1-5z" stroke="#7f77dd" stroke-width="1.2" stroke-linecap="round" stroke-linejoin="round"/>
    </svg>
    <span style="font-size: 11px; font-weight: 500; letter-spacing: 0.05em; text-transform: uppercase; color: #534AB7;">TL;DR</span>
  </div>
  <div style="font-size: 13px; color: #3C3489; line-height: 1.65;">
    Every registered object starts with the same fields: <strong>Name</strong>, <strong>Alias</strong>, <strong>Entity</strong>, plus a <strong>Properties</strong> section (<strong>Description</strong>, <strong>Permissible Purpose</strong>, <strong>Group</strong>, <strong>Keywords</strong>). This page defines them once so the per-object user guides don't repeat them.
  </div>
</div>

## The common fields

Create form opens with Name, Alias, and Entity. A Properties section underneath that holds the Description, Permissible Purpose, Group, and Keywords.

<table class="attr-table">
  <thead>
    <tr>
      <th style="width: 22%;">Field</th>
      <th>What it's for</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td class="field-cell">Name<span class="req">Required</span></td>
      <td>The display name for the object and is shown on the object's details page. Keep it clear: <code>Account Balance</code>, not <code>Bal_v3_FINAL</code>.</td>
    </tr>
    <tr>
      <td class="field-cell">Alias<span class="req">Required</span></td>
      <td>A short identifier used to reference the object in code and definitions, like <code>account_balance</code>. Follow Python identifier rules: letters, numbers, and underscores only.</td>
    </tr>
    <tr>
      <td class="field-cell">Entity<span class="req">Required</span></td>
      <td>What the object is about and the level it is decisioned at: Application, Customer, Account, and so on. This sets the grain, meaning what a single row represents. Choose from the configured list. Reusable objects like Reports and Global Functions don't have an Entity.</td>
    </tr>
  </tbody>
</table>

### Properties

<table class="attr-table">
  <thead>
    <tr>
      <th style="width: 22%;">Property</th>
      <th>What it's for</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td class="field-cell">Description<span class="req">Required</span></td>
      <td>A short summary of what the object is and why it exists. Other people will read this when they reference your object.</td>
    </tr>
    <tr>
      <td class="field-cell">Permissible Purpose<span class="req">Required</span></td>
      <td>Tags that control where the object can be used, like <code>Underwriting</code> or <code>PII</code>. Tag a Data Element as <code>PII</code> and the platform flags any attempt to use it where PII isn't allowed. Available tags are configured in Settings.</td>
    </tr>
    <tr>
      <td class="field-cell">Group<span class="req">Required</span></td>
      <td>A folder for organizing related objects. Group also controls how the object is ordered and displayed on details pages. Search existing groups or create a new one.</td>
    </tr>
    <tr>
      <td class="field-cell">Keywords</td>
      <td>Optional search tags. Add if they help discoverability; otherwise skip.</td>
    </tr>
  </tbody>
</table>

:::note[Exceptions]
Reports and Global Functions are reusable across the platform, so they have no Entity. Reports also have no Permissible Purpose.
:::

<!-- TODO: confirm the Settings path for Permissible Purposes and add a screenshot of the Properties section. -->

## What's Next

- Register your first object: [Register a Table](/user-guide/how-tos/register-a-table/) or [Register a Data Element](/user-guide/how-tos/register-a-data-element/).
- Once registered, send it for [approval](/user-guide/how-tos/approve-an-object/) so it can be used outside your draft workspace.