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

# Application Management

> Comprehensive guide to creating, configuring, and managing social.plus applications through the portal, including regional deployment and organizational settings.

[YouTube video player](https://www.youtube.com/embed/Ym4XhKWaEPA?si=dJOPrEacTT7SKamk)

> [!NOTE]
>
> Create and govern up to 50 applications per organization, selecting an immutable data residency region and maintaining clear naming, lifecycle, and audit practices.

> **Create**
>
> Add new application & region

> **Search & Filter**
>
> Locate by ID / name / plan / region

> **Edit Metadata**
>
> Rename application safely

> **Region Strategy**
>
> Choose optimal data residency

> **Scale**
>
> Track approach to 50 app limit

> **Governance**
>
> Apply naming & ownership rules

## Access

**1. Sign In**

Use Email & Password or SAML SSO.

**2. Navigate**

Portal sidebar → My Applications.

**3. Review Inventory**

Scan list, use search & sort tools.

## Create an Application

**1. Open Creation**

Click “Create Application”.

**2. Name & Region**

Enter unique name; select region (EU, SG, US).

**3. Validate Quota**

Confirm you remain within 50 application cap.

**4. Confirm**

Click Next → Confirm to finalize.

**5. Post-Create Tasks**

Distribute app ID, configure security (Secure Mode, tokens) in Console.

> [!WARNING]
>
> The selected region cannot be changed after creation. Choose based on latency, data residency, and compliance constraints.

## Edit an Application

**1. Locate**

Search by APP ID or Name or filter by Plan / Region.

**2. Select**

Click “Edit” next to target application.

**3. Update**

Modify name or descriptive metadata (region locked).

**4. Save**

Click Save; verify updated label appears in listing.

**5. Communicate**

Notify teams if name changes impact tooling / dashboards.

## Region Selection Strategy

> **Latency**
>
> Pick geographically closest region to majority user base to reduce round‑trip time.

> **Data Residency**
>
> Align with legal / compliance restrictions (e.g., EU data constraints).

> **Failover Architecture**
>
> Use separate applications in multiple regions rather than expecting in‑place region migration.

> **Growth Planning**
>
> Reserve name conventions (e.g., product-env-region) to avoid collisions.

## Naming & Governance

**Pattern**

Use pattern: ` <product>-<env>-<region>`

(e.g., chat-prod-eu).

**Ownership**

Assign an accountable owner for each application for audits & incident response.

**Tags (If Supported)**

Apply tags for cost center, environment, and compliance classification.

**Change Control**

Document any rename in central log (date, old, new, approver).

## Capacity & Limits

> [!NOTE]
>
> You may create up to 50 applications. Contact support to request a higher cap with justification (e.g., multi-tenant SaaS segmentation).

> **When to Request Increase**
>
> Approaching ≥ 45 apps with planned roadmap growth & clear separation rationale.

> **Consolidation First**
>
> Audit unused / duplicate staging apps before expansion.

## Metrics & Monitoring

| Metric | Purpose | Healthy Signal | Action Trigger |
| - | - | - | - |
| App Count Utilization | Track usage vs cap (50) | \< 90% | ≥ 90% → consolidation review / raise request |
| Naming Compliance % | Standardized names / total | 100% | \< 95% → enforce pattern |
| Orphaned Apps | Apps without owner | 0 | > 0 → assign or archive |
| Edit Frequency | Name changes per month | Low & intentional | Spike → investigate process drift |
| Region Distribution | Apps per region | Balanced vs strategy | Unexpected cluster → latency review |

## Troubleshooting

| Issue | Likely Cause | Resolution |
| - | - | - |
| Cannot create new app | Reached 50 cap | Archive unused or request limit increase |
| Region incorrect post-creation | Mis-selection | Create new app in correct region; migrate data; deprecate old |
| App not found via search | Typo / stale name | Use APP ID or confirm rename log |
| Frequent renames | Lack of naming standards | Adopt enforced pattern & approval gate |
| Latency complaints | Suboptimal region | Plan transition via new region app & user migration |

## Best Practices

> **Immutable Region Awareness**
>
> Highlight region lock in internal onboarding docs.

> **Inventory Reviews**
>
> Quarterly review for orphaned or redundant staging apps.

> **Documentation Sync**
>
> Update internal runbooks when app names change.

> **Separation by Compliance Tier**
>
> Isolate higher compliance workloads to dedicated applications for clearer audit scoping.

## Quick Reference

> **Limit**
>
> 50 applications

> **Region**
>
> EU • SG • US

> **Pattern**
>
> product-env-region

> **Owner**
>
> Single accountable contact

## Related

> **[Getting Started](/analytics-and-moderation/social+-portal/getting-started.md)**
>
> Portal sign‑in & SSO

> **[Security](/analytics-and-moderation/console/settings/security.md)**
>
> Secure Mode & keys

> [!NOTE]
>
> Need to adjust the application cap? Prepare justification (use cases, consolidation audit) before contacting support.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.