Databricks Identity and Team Mappings

Mappings connects Databricks identities to LakeSentry’s organizational model. It is the foundation for reliable chargeback, budgets, and attribution quality.

Tabs

Principals

Principals are Databricks users, service principals, and groups observed in billing, query history, jobs, access metadata, and other system tables.

Use this tab to:

• Assign a principal to a team.
• Review unmapped users and service principals.
• Identify principal aliases or service accounts that should be owned by a platform team.
• Open a principal detail page for recent cost and activity.

Organization

The organization hierarchy is:

Org Unit → Department → Team

Teams are the leaf nodes used by attribution rules and budgets. Departments and org units provide rollups for reporting and budget tracking.

How mappings affect attribution

When no exact or pattern attribution rule matches, LakeSentry falls back to identity and ownership signals. A mapped user or resource owner can assign spend to a team. If the principal is known but not mapped, LakeSentry can show the principal while keeping the team allocation incomplete.

Recommended workflow

1. Build the org unit, department, and team structure.
2. Map high-spend principals first.
3. Map shared service principals to the owning platform or data team.
4. Review Cost Allocation for remaining unattributed spend.
5. Add rules only where mappings and ownership are not enough.