> ## Documentation Index
> Fetch the complete documentation index at: https://betterdatainc.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Admin Overview

> Comprehensive overview of tenant administration and configuration

# Admin Overview

Tenant administration features allow you to configure and manage your organization's settings, users, policies, and integrations. This guide provides an overview of all admin capabilities.

<Warning>
  **Scope**: All features documented here are tenant-scoped and require organization admin permissions. SuperAdmin features (tenant provisioning, entitlement assignment) are not included in this documentation.
</Warning>

## Understanding Tenant Admin vs SuperAdmin

### Tenant Admin (This Documentation)

**What it covers:**

* Organization-level configuration
* User and role management within your organization
* Policy configuration for your organization
* Integration setup for your organization

**Who uses it:**

* Organization administrators
* Policy administrators
* Configuration administrators

**Scope:**

* Limited to your organization
* Cannot manage other organizations
* Cannot change platform-level settings

### SuperAdmin (Excluded from This Documentation)

**What it covers:**

* Platform-level administration
* Tenant provisioning
* Entitlement assignment
* Billing admin operations
* System-wide analytics

**Who uses it:**

* Platform administrators
* Better Data staff

**Scope:**

* Platform-wide
* Can manage all organizations
* Can change platform-level settings

## Configuration Model

Better Data SCM uses a three-tier customization model:

### SYSTEM\_FIXED

Core system values that cannot be changed (workflow states, RBAC scopes, billing tiers).

### TEMPLATED\_OVERRIDE

Industry pack provides defaults, but you can override (location types, payment terms, GL accounts).

### TENANT\_DEFINED

No system defaults; you define all values (budget codes, channel policies, API keys).

See [Customization Model](/admin/customization-model) for details.

## Admin Categories

<CardGroup cols={3}>
  <Card title="Users & Roles" icon="users" href="/admin/users-roles">
    Manage users, roles, and permissions
  </Card>

  <Card title="Organization Settings" icon="building" href="/admin/organization-settings">
    Configure organization-level settings
  </Card>

  <Card title="Locations" icon="map-pin" href="/admin/locations">
    Manage locations, types, and activities
  </Card>

  <Card title="Channel Policies" icon="chart-line" href="/admin/channel-policies">
    Configure channel-specific policies
  </Card>

  <Card title="ATP Policies" icon="shield" href="/admin/atp-policies">
    Configure Available to Promise policies
  </Card>

  <Card title="Replenishment Config" icon="refresh-cw" href="/admin/replenishment-config">
    Configure replenishment rules
  </Card>

  <Card title="Finance Configuration" icon="dollar-sign" href="/admin/finance-configuration">
    Budget codes, GL accounts, payment terms
  </Card>

  <Card title="Audit & Compliance" icon="clipboard-check" href="/admin/audit-compliance">
    Compliance rules and audit configuration
  </Card>

  <Card title="Integrations" icon="plug" href="/admin/integrations">
    API keys, webhooks, external systems
  </Card>

  <Card title="Trust & Trace" icon="fingerprint" href="/admin/trust-trace">
    Signal tags, tokenizer, trade networks
  </Card>

  <Card title="Alerts Config" icon="bell" href="/admin/alerts-config">
    Configure alert destinations and types
  </Card>

  <Card title="Taxonomies" icon="tags" href="/admin/taxonomies">
    Manage product taxonomies
  </Card>
</CardGroup>

## Configuration Map

See [Configuration Map](/admin/configuration-map) for a complete index of all configuration areas organized by category with customization tier indicators.

## Getting Started

### 1. Understand Your Industry Pack

Your industry pack determines:

* Default location types
* Default reason codes
* Default payment terms
* Default GL account templates
* Default role templates

See [Industry Packs](/concepts/industry-packs) for details.

### 2. Review Configuration Map

Use the [Configuration Map](/admin/configuration-map) to:

* Find configuration areas
* Understand customization tiers
* Navigate to specific configuration pages

### 3. Configure Core Settings

Start with core settings:

1. **Organization Settings**: Basic organization information
2. **Users & Roles**: Set up users and assign roles
3. **Locations**: Create and configure locations
4. **Channel Policies**: Configure sales channels

### 4. Configure Advanced Features

Then configure advanced features:

1. **Finance Configuration**: Set up GL accounts and payment terms
2. **Policies**: Configure ATP and inventory policies
3. **Integrations**: Set up API keys and webhooks
4. **Trust & Trace**: Configure signal tags and tokenization

## Common Configuration Workflows

### Initial Setup

1. **Organization Settings**: Configure basic organization information
2. **Industry Pack**: Verify industry pack is correct
3. **Locations**: Create initial locations
4. **Users**: Add users and assign roles
5. **Channels**: Configure sales channels
6. **Policies**: Set up channel and ATP policies

### Ongoing Administration

1. **User Management**: Add/remove users, update roles
2. **Policy Updates**: Adjust policies based on business needs
3. **Location Management**: Add/modify locations
4. **Integration Management**: Update API keys, webhooks
5. **Compliance**: Review and update compliance rules

## What Success Looks Like

### Configuration Success

* ✅ All configuration areas properly set up
* ✅ Users have appropriate roles and permissions
* ✅ Policies align with business requirements
* ✅ Integrations working correctly
* ✅ Compliance rules configured

### Administration Success

* ✅ Users can access needed features
* ✅ Policies drive correct behavior
* ✅ Integrations functioning properly
* ✅ Compliance requirements met
* ✅ Configuration changes documented

## Common Pitfalls

### 1. Not Understanding Customization Tiers

**Problem**: Trying to change SYSTEM\_FIXED values or not understanding template overrides.

**Solution**: Understand the customization model:

* Know what's SYSTEM\_FIXED (cannot change)
* Understand TEMPLATED\_OVERRIDE (pack defaults + override)
* Use TENANT\_DEFINED for custom configurations

**How to avoid**: Review [Customization Model](/admin/customization-model) before making changes.

### 2. Not Using Pack Defaults

**Problem**: Creating custom configurations when pack defaults would work.

**Solution**: Start with pack defaults:

* Use pack defaults when they fit
* Only customize when necessary
* Document why you're customizing

**How to avoid**: Review pack defaults before creating custom configurations.

### 3. Not Documenting Customizations

**Problem**: Making customizations without documenting why.

**Solution**: Document all customizations:

* Why you customized
* What you changed
* When you changed it
* Who approved it

**How to avoid**: Make documentation part of customization workflow.

### 4. Not Testing Configuration Changes

**Problem**: Making configuration changes without testing.

**Solution**: Test configuration changes:

* Test in non-production first
* Verify changes work as expected
* Roll back if issues occur

**How to avoid**: Make testing part of configuration workflow.

## Troubleshooting

### Configuration Not Taking Effect

**Symptoms**: Configuration changes not reflected in system behavior.

**Possible causes:**

1. Changes not saved
2. Cache not cleared
3. Permissions insufficient
4. Configuration dependency issue

**Steps to resolve:**

1. Verify changes were saved
2. Clear browser cache
3. Check user permissions
4. Review configuration dependencies
5. Refresh page and check again

### Can't Access Admin Features

**Symptoms**: Admin features not accessible or not visible.

**Possible causes:**

1. Insufficient permissions
2. Role not assigned
3. Organization context missing
4. Feature not enabled

**Steps to resolve:**

1. Check user has tenant admin role
2. Verify role assignments
3. Check organization context
4. Verify feature is enabled
5. Contact organization administrator

### Configuration Conflicts

**Symptoms**: Configuration changes conflict with existing settings.

**Possible causes:**

1. Conflicting policies
2. Dependency issues
3. Validation errors
4. System constraints

**Steps to resolve:**

1. Review configuration dependencies
2. Check for conflicting policies
3. Review validation errors
4. Adjust configuration to resolve conflicts
5. Contact support if needed

***

## Related Pages

* [Customization Model](/admin/customization-model)
* [Configuration Map](/admin/configuration-map)
* [Users & Roles](/admin/users-roles)
* [Organization Settings](/admin/organization-settings)

***

## Permissions & Roles

<Warning>
  Admin features require tenant admin permissions. These features are organization-scoped and not available in SuperAdmin. Contact your organization administrator if you need admin access.
</Warning>