Rich User and Organization Data

Business Problem

As CEO, you want your application to feel intelligent from day one. What slows down most SaaS products is forcing end-users and customer success reps to manually enter company and personal data. That creates onboarding friction, frustrates customers, and leads to incomplete or inaccurate profiles.

For your go-to-market team: reps waste hours researching accounts, building lists, and cleaning up CRM entries instead of selling. Forecasts slip because pipeline data is fragmented.
For your operations team: RevOps spends valuable time de-duping records, normalizing fields, and reconciling conflicts across tools. Every new enrichment vendor just adds more sprawl.
For your customers: the product feels dumb if they have to repeatedly tell you who they are and where they work. That poor first impression makes adoption harder.

With Baseplate we want to kill all these issues and ensure we've got rich data on customers and users built into the system.

Jobs-to-be-Done

Your job as CEO: You need your product to impress users immediately with a personalized, intelligent experience — without requiring extra manual steps.
Your RevOps team’s job: They need clean, enriched company and contact data flowing into every system automatically, so they can focus on higher-value work instead of cleanup.
Your reps’ job: They need instant clarity on which organization a user belongs to, who the decision-makers are, and how to reach them — so they can accelerate adoption and revenue growth.

This feature “hires” Baseplate to do the heavy lifting: automatically mapping users and tenants to verified organization profiles and keeping that data consistent across your product.

Inspirational Examples

Clearbit Reveal: Enriches web traffic in real time, giving sales teams firmographics without extra input. It feels magical — and that’s how your app should feel to new users.
LinkedIn Sales Navigator: Surfaces org charts, job changes, and warm introductions instantly. That’s the kind of actionable context your users will value.
Okta Universal Directory: Anchors identities across systems with a stable ID. Just like Baseplate’s use of organization_id and person_id, it prevents duplication and keeps your data clean as you scale.

How It Works

Seamless Login Experience - When a new user signs up, Baseplate parses their corporate email domain (acme.com). Without them lifting a finger, the system queries Creso.ai’s database.
Automatic Enrichment - Baseplate maps each organization and person to a single, verified Creso.ai organization_id and person_id, pre-populating the profile with company details (industry, size, HQ) and user context.
Tenant Mapping - The user is automatically associated with their company’s tenant record. If the org already exists, they’re added. If not, a new enriched record is created.
Data Propagation - Every app you build on Baseplate inherits this enriched data automatically. That means personalization, analytics, and support functions start “fully loaded.”
Golden Record Guarantee - By anchoring to global IDs, you prevent duplicate orgs, orphan contacts, and forecast errors. Your product scales cleanly instead of creating chaos.

Applications should know customers the moment they log in. You can then provide a seamless, intelligent experience that delights your users, saves your teams time, and compounds in value as you grow.

Pages and Screens

Login Handler

This is the first interaction point where the enrichment flow begins. A user signs up or logs in with their corporate email (jane.doe@acme.com). Baseplate:

Parses the top level domain
Queries Creso.ai for rich company data
Sets up the tenant if not present in system
Queries Creso.ai (with enrichment) for user data
Sets up the user in the systems

From the user’s perspective, nothing changes — the screen looks like a standard login page. The magic is aumatic provisioning of a built out tenant, detailed user data (if available) and immediate allocation to the correct organization.

Delay Mapping Configuration

A setting available to all customers accessible only to System Roles (e.g., Customer Administrators, System Administrators) that allows customer specific configuration for how automated tenant mapping is handled for their organization. By default, Baseplate automatically associates new users with the tenant if their email TLD matches the tenant’s domain. This screen introduces an optional control: the ability to delay mapping or turn off mapping and require explicit admin approval before users are added.

When delay mapping or turn off mapping setting is enabled, new users from the tenant’s domain are placed in a Pending state rather than being automatically mapped. A notification is sent to all tenant administrators, who can then approve or reject each pending user. Approved users are added to the tenant as normal. Rejected users are routed to a "Standalone Users" tenant - ensuring they still have access to public-facing features without cluttering the tenant’s membership.

This configuration provides admins with an extra layer of governance and control over who can join their tenant — useful in industries with sensitive data, strict compliance requirements, or higher security needs.

Delayed Auto Mapping automatically allocates users to a given tenant after 72 hours of inaction. This forces action on any added users.

Pending Users Screen

The Pending Users screen provides System Roles (Customer Administrators, System Administrators) with a centralized place to review, approve, or reject users whose corporate email domains match the tenant but were not automatically mapped due to the Delay Automated Mapping setting.

When a new user attempts to log in or create an account, they are flagged as Pending. This screen lists all such users, including their email address, full name (if available), associated domain, and time of request. Administrators can take action on each pending user individually, or select multiple users for bulk approval/rejection.

Approve: The user is added to the tenant as a full member.
Reject: The user is redirected to the Standalone Users Tenant, preventing access to tenant-specific resources.
No Action: The user remains pending until an admin takes action.

This screen ensures tenant admins maintain precise control over who joins their tenant while still allowing rejected users a fallback workspace.

Customer Profile Screen

This is the canonical “home” for organizational data within the application. It displays enriched firmographic data for the account including (industry, size, and key endpoints), org chart previews, and associated users already mapped from your tenant. The screen provides admins and CS managers with a single source of truth about the customer organization. From here, users can view the following information about the company:

Field ID	Field Name	Field Description
name	Name	Primary name of the entity (Diffbot Docs)
fullName	Legal Name	Full formal name for the entity (Diffbot Docs)
allNames	Other Names	All names used, including nicknames, full names, and transliterations (Diffbot Docs)
type	Type	Primary entity type (e.g., Corporation, Organization) (Diffbot Docs)
naicsClassification2017	Industry	Primary industry for the company
description	Description	A few sentences describing the entity (Diffbot Docs)
foundingDate	Founding Date	The date the organization was founded (Diffbot Docs)
homepageUri	Homepage	Link to the homepage (Diffbot Docs)
location	Location	Main organizational location (address, city, etc.) (Diffbot Docs)
logo	Logo	Graphic mark or emblem of the institution (Diffbot Docs)
phoneNumbers	Phone Numbers	Contact phone numbers of the organization (Diffbot Docs)
Social Media
blogUri	Blog	Link to the entity’s blog (Diffbot Docs)
linkedInUri	LinkedIn	Link to the organization's LinkedIn profile (Diffbot Docs)
twitterUri	Twitter	Link to the Twitter profile (Diffbot Docs)
wikipediaUri	Wikipedia	Link to the Wikipedia page (Diffbot Docs)
facebookUri	Facebook	Link to the Facebook profile (Diffbot Docs)
githubUri	GitHub	Link to the GitHub profile (Diffbot Docs)

This data is provided in view only mode in the application. All data is provided to System Roles. Name, Description, Homepage and social media links are provided for all other users.

Each of the above pieces of information is pulled in "live" based on the linked Creso ID for the company.

Type: Full Page

New Customer Standard Onboarding Wizard

For new customer tenants, the onboarding wizard includes an enrichment-driven step. Instead of asking admins to manually enter company details (name, size, industry, website, etc.), the system auto-fills this information based on the domain lookup. The step presents the enriched data in a review-and-confirm format, so the admin just verifies accuracy instead of typing. This reduces onboarding time dramatically and creates trust in the product’s intelligence.

Type: Wizard Step

Notes

If Diffbot or Creso data is missing, fallback to user-provided values.
Auto-suggestion of tags or departments may be added via LLM prompts.
Consider permission gating to prevent overexposure of personally identifiable info (PII) depending on user role.
Should support rendering in modal or full-page format depending on usage context (e.g. modal in team directory, full page in profile navigation).