4.2 Company Information, Licenses & Object Manager

Company Information, Licenses & Object Manager

Quick Answer: The Company Information page in Salesforce Setup serves as the master record of your organization's tenant configuration, detailing your unique Salesforce Organization ID, default locale and time zone, fiscal calendar type, currency settings, remaining User and Feature Licenses, and Data/File Storage consumption. For configuring data structures, administrators rely on two primary hubs: the Object Manager for detailed, field-by-field and layout customizations, and Schema Builder for visual, drag-and-drop entity-relationship modeling.

Building and maintaining an effective Salesforce environment requires administrators to understand the underlying infrastructure, capacity constraints, and object architecture of their organization. The Salesforce Platform Foundations exam tests your understanding of where vital tenant metadata resides, how licensing governs user capabilities, how storage quotas function, and how to access declarative modeling tools.

---

The Company Information Page: The Organization's DNA

Located under Setup -> Company Settings -> Company Information, this page acts as the system passport for your Salesforce organization. It provides essential organization-level metadata that establishes the operating baseline for all platform functionality.

+-----------------------------------------------------------------------------------------+
| Setup > Company Settings > Company Information                                          |
+-----------------------------------------------------------------------------------------+
| Organization Detail                                                                     |
|   ├── Organization Name:             Global Logistics Enterprises                       |
|   ├── Salesforce Organization ID:     00D500000001234 (15-char) / 00D500000001234EAA   |
|   ├── Organization Edition:          Enterprise Edition                                 |
|   ├── Instance:                      NA142 (Hyperforce / Regional Pod)                  |
|   └── Primary Contact:               admin@globallogistics.com                          |
| Locale Settings (Organization Baseline)                                                 |
|   ├── Default Locale:                English (United States)                            |
|   ├── Default Language:              English                                            |
|   └── Default Time Zone:             (GMT-05:00) Eastern Standard Time (America/New_York)|
| Currency & Fiscal Settings                                                              |
|   ├── Currency:                      USD ($) - Single Currency / Multi-Currency Active  |
|   └── Fiscal Year:                   Standard (Starts in January) vs Custom             |
| Storage Usage Summary                                                                   |
|   ├── Data Storage:                  14% of allocation used (records)                   |
|   └── File Storage:                  8% of allocation used (files, attachments)         |
+-----------------------------------------------------------------------------------------+

Critical Company Information Fields

1. Salesforce Organization ID (Org ID):

   • A unique 15-character (or 18-character case-insensitive) identifier assigned specifically to your Salesforce tenant.
   • Why It Matters: The Org ID is mandatory whenever you open a customer support case with Salesforce, purchase or provision additional user licenses, authorize developer sandboxes, configure Single Sign-On (SSO) identity providers, or establish secure API connections with external platforms.
   • Exam Tip: Do not confuse the Org ID with user IDs or individual record IDs. The Org ID identifies the entire database tenant.

2. Default Locale, Language, and Time Zone:

   • Establishes the fallback operating standard for the organization.
   • When an administrator creates a new user, that user automatically inherits the organization's default locale, language, and time zone.
   • Users can subsequently override these settings in their Personal Settings without altering the corporate default.

3. Fiscal Year Configurations:

   • Standard Fiscal Year: Follows the Gregorian calendar and consists of 12 consecutive months. The fiscal year can begin on the first day of any month (e.g., January 1 for traditional calendar years, February 1 for retail cycles, or July 1 for governmental agencies).
   • Custom Fiscal Year: Designed for enterprises with intricate accounting structures, such as 4-4-5 (four weeks, four weeks, five weeks per quarter), 4-5-4, 5-4-4, or 13-period accounting cycles.
   • CRITICAL EXAM WARNING: Enabling Custom Fiscal Years is permanent and irreversible. Once an administrator activates Custom Fiscal Years in Setup, the feature cannot be disabled or reverted back to Standard Fiscal Years. Furthermore, activating Custom Fiscal Years impacts standard opportunity forecasting and historical reporting metrics.

4. Currency Settings:

   • Single Currency: The default configuration for new Salesforce environments. All monetary fields display values in a single corporate currency.
   • Multiple Currencies: Organizations operating globally can activate Multiple Currencies to allow opportunities, quotes, and reports to reflect transactions in diverse international currencies. Administrators define a Corporate Currency as the baseline benchmark and manage conversion exchange rates between active secondary currencies. Similar to custom fiscal years, once Multiple Currencies is enabled, it cannot be disabled.

5. Storage Capacity Limits: Salesforce allocates two distinct types of storage quotas based on your edition and user license count:

   • Data Storage: Stores standard and custom database records (e.g., Accounts, Contacts, Leads, Opportunities, Custom Objects).
     • Almost all standard and custom records consume 2 KB of data storage per record.
     • Notable exceptions include Campaign Member records (1 KB), Person Account records (4 KB), EmailMessage records (size varies with the message), and Knowledge article records.
   • File Storage: Stores physical digital assets, including documents, file attachments, ContentVersion files, images, Chatter group files, and site assets.
   • Allocations: Each edition receives a baseline data and file storage allocation that grows with the number of user licenses. The Storage Usage page in Setup shows current consumption by object and file type.

---

Salesforce Licensing: User Licenses vs. Feature Licenses

Every individual who accesses Salesforce requires appropriate licensing. Understanding the difference between User Licenses and Feature Licenses is one of the most frequently tested concepts on the exam.

+-----------------------------------------------------------------------------------------+
| USER LICENSES (Baseline Identity & Access)                                              |
| [ Each active user MUST have EXACTLY ONE User License assigned ]                        |
|                                                                                         |
|   ┌─────────────────────────────────────────────────────────────────────────────────┐   |
|   │ Full "Salesforce" License                                                       │   |
|   │ Access to all standard CRM objects (Leads, Accounts, Contacts, Opps, Cases)    │   |
|   └─────────────────────────────────────────────────────────────────────────────────┘   |
|   ┌─────────────────────────────────────────────────────────────────────────────────┐   |
|   │ "Salesforce Platform" License                                                   │   |
|   │ Access to custom objects, accounts, contacts, reports, but NO standard CRM      │   |
|   │ objects (no Leads, Opportunities, Campaigns, or Cases).                         │   │
|   └─────────────────────────────────────────────────────────────────────────────────┘   |
+-----------------------------------------------------------------------------------------+
                                          │
                                          │ Assigned User
                                          ▼
+-----------------------------------------------------------------------------------------+
| FEATURE LICENSES (Additive Tools & Specific Capabilities)                               |
| [ Add-on checkboxes granted to users who already possess a base User License ]          |
|                                                                                         |
|   [x] Marketing User:       Authorizes creation and execution of Campaigns              |
|   [x] Service Cloud User:   Unlocks Service Console, Omni-Channel, and CTI widgets      |
|   [x] Knowledge User:       Allows authoring, publishing, and archiving Knowledge items |
|   [x] CRM Content User:     Grants access to Salesforce CRM Content libraries          |
+-----------------------------------------------------------------------------------------+

Direct Comparison: User Licenses vs. Feature Licenses

---

Object Manager: Central Hub for Data Customization

Accessed directly via Setup -> Object Manager, this console is the primary workspace for declarative customization of database objects. Rather than writing SQL tables or database migrations, administrators navigate through standard and custom objects to configure fields, layouts, and automation rules.

+-----------------------------------------------------------------------------------------+
| Setup > Object Manager > Account                                                        |
+-----------------------------------------------------------------------------------------+
| Account Object Subsections:                                                             |
|   ├── Details:                  Object API name (Account vs Custom_Object__c), labels   |
|   ├── Fields & Relationships:   Standard/custom fields, formulas, data types, FLS       |
|   ├── Page Layouts:             Field positioning, related lists, detail sections       |
|   ├── Lightning Record Pages:   Dynamic components configured via Lightning App Builder |
|   ├── Buttons, Links & Actions: Custom quick actions, URL buttons, modal forms          |
|   ├── Record Types:             Business processes, distinct picklists, layout mapping  |
|   ├── Compact Layouts:          Header highlights panel and mobile summary cards        |
|   ├── Validation Rules:         Formula criteria enforcing data completeness & formats  |
|   └── Object Limits:            Monitoring consumption against platform limits (e.g. 500)|
+-----------------------------------------------------------------------------------------+

Essential Subsections within an Object

1. Fields & Relationships: Where administrators create custom fields (e.g., text, currency, date, picklist, formulas), establish relationship links between objects (Lookups, Master-Detail), and configure Field-Level Security (FLS).
2. Page Layouts vs. Lightning Record Pages:
   • Page Layouts: Control which fields, sections, and related lists are visible, required, or read-only on traditional detail pages and mobile layouts.
   • Lightning Record Pages: Built with the drag-and-drop Lightning App Builder, allowing administrators to construct responsive modern pages incorporating tabs, accordions, dynamic component visibility, and path guidance.
   • Dynamic Forms: Lets administrators place individual fields and field sections directly on a Lightning record page in Lightning App Builder instead of one large Record Detail block inherited from the page layout. Each field or section can have visibility rules (for example, show Discount Reason only when Discount is above 15%). Dynamic Forms work on custom objects and many standard objects, and they reduce the need to maintain multiple page layouts.
3. Record Types: Allows administrators to offer different business processes, picklist values, and page layouts to different users based on their role or profile (e.g., separating Enterprise Accounts from Small Business Accounts).
4. Compact Layouts: Defines the key fields (up to 10) displayed in the Highlights Panel at the very top of a record page in Lightning Experience and on mobile cards.
5. Validation Rules: Custom formulas that verify whether data entered by a user satisfies specific business standards before the record is saved to the database. If the formula evaluates to True, an error message blocks the save.
6. Object Limits: Displays real-time metrics showing how many custom fields, validation rules, relationship fields, and roll-up summaries have been used out of the maximum platform limits permitted for that object.

---

Schema Builder: Interactive Visual Data Modeling

While the Object Manager provides a tabular, list-based interface for managing objects one at a time, the Schema Builder (found in Setup -> Schema Builder) provides an interactive, drag-and-drop graphical canvas of your organization's entire data model.

+-----------------------------------------------------------------------------------------+
| Setup > Schema Builder                                                                  |
+-----------------------------------------------------------------------------------------+
| [ Palette (Objects / Elements) ]  |  [ Interactive Modeling Canvas ]                   |
| ├── Objects:                      |  ┌──────────────────┐       ┌────────────────────┐  |
| │   [x] Account                   |  │ Account          │       │ Contact            │  |
| │   [x] Contact                   |  ├──────────────────┤   ┌───┤────────────────────┤  |
| │   [x] Opportunity               |  │ Account Name     │   │   │ First Name         │  |
| │   [x] Invoice__c                |  │ Phone            │   │   │ Last Name          │  |
| ├── Elements (Drag onto Canvas):  |  │ Annual Revenue   │   │   │ AccountId (Lookup) ├──┘
| │   [+] Custom Object             |  └────────┬─────────┘   │   └────────────────────┘  |
| │   [+] Text Field                |           │             │                           |
| │   [+] Currency Field            |           └─────────────┘ (Lookup Relationship Line)|
| │   [+] Master-Detail Rel.        |                                                     |
+-----------------------------------------------------------------------------------------+

Capabilities and Advantages of Schema Builder

• Visual Entity-Relationship Diagram (ERD): Graphically displays standard and custom objects as interconnected tables. Lines between objects indicate Lookup and Master-Detail relationships.
• Selective Display: Administrators can filter the canvas to show all objects, selected objects, or only custom objects, reducing visual clutter.
• Rapid Prototyping and Field Creation: Administrators can drag new custom objects or custom field data types directly from the Elements palette onto an object table on the canvas. The field is created immediately in the database without navigating through the multi-step Object Manager wizard.
• Limitations: While Schema Builder creates the field and underlying metadata instantly, it does not automatically add the newly created field to existing Page Layouts. Administrators must subsequently edit Page Layouts in Object Manager if they want the field displayed on standard layout pages.

---

System Status, Trust & Infrastructure Monitoring

Salesforce operates a multi-tenant cloud infrastructure where organizations reside on specific regional instances or "pods" (e.g., NA142, EU31, AP25) or cloud environments like Hyperforce.

• Identifying Your Instance: Administrators can locate their instance identifier on the Company Information page. Modern My Domain URLs (such as yourcompany.my.salesforce.com) no longer include the instance name, so the browser address bar is not a reliable place to look.
• Salesforce Trust (status.salesforce.com): The public transparency and system status portal provided by Salesforce. Administrators and stakeholders visit this site to:
  • Check real-time service availability and health metrics for their specific instance.
  • Review ongoing service disruptions, performance degradations, or security advisories.
  • Inspect upcoming scheduled maintenance windows, system upgrades, and seasonal release deployments (Spring, Summer, Winter).