Project: Define your operational boundary

Project

A project is the top-level container for your SendPromptly integration. It defines the operational boundary for events, templates, tokens, and delivery behavior.

Most teams use one project per product or application domain. This keeps ownership clear and prevents unrelated notification streams from sharing configuration.

What belongs to a project

• Environment-specific API tokens
• Event keys and template versions
• Delivery configuration and logs
• Team access and operational ownership

Project boundary guidelines

Use separate projects when products have different recipients, compliance requirements, or ownership teams. Keep a single project when services share the same customer communication domain and lifecycle.

Recommended naming conventions

Use stable names tied to business context, for example:

• core-app-notifications
• marketplace-ops
• billing-events

Avoid temporary names based on sprint or campaign labels.

Access and governance practices

• Limit production access to required operators.
• Keep least-privilege access for development environments.
• Review project membership regularly.
• Document project ownership and on-call responsibility.

Lifecycle management

1. Create project and environments.
2. Define event taxonomy and template standards.
3. Integrate ingestion from backend services.
4. Monitor delivery KPIs and error trends.
5. Iterate safely with versioned templates and environment isolation.

A well-defined project model reduces integration drift and gives product, support, and engineering teams a shared operational view.