Service Archetypes
Internal Business App
Internal business apps often support finance, operations, HR, support, or back-office workflows. They may have fewer users than public apps but can carry high business and data risk.
Common requirements
- SSO and group-based authorization.
- Audit logs for privileged actions.
- Data classification and retention rules.
- Clear owner for business process changes.
- Backup and restore for important records.
- Support model for business-hours or critical operations.
Architecture shape
Delivery guidance
- Use preview or staging environments for business validation.
- Keep environment data synthetic unless approved otherwise.
- Document approval flows for workflow or data changes.
- Use feature flags for high-impact process changes.
- Define support hours and escalation clearly.
Readiness checks
Before production, confirm:
- Business owner has validated critical workflows.
- Admin roles are separated from normal user roles.
- Audit logs capture privileged changes.
- Data export behavior is reviewed.
- Support hours match business process criticality.
Watchouts
- Internal does not mean low risk.
- Spreadsheet exports often bypass platform controls.
- Business admins may need separate privileged access review.
- Manual workflow changes can have financial or compliance impact.