← All project stories

Architecture design / Proposed system

Automation intake,
with a clear next step.

Make ideas easy to submit, give reviewers the context they need, and keep decisions traceable.

This is a proposed architecture, not a deployed-system claim. This page does not submit requests or connect to an enterprise tenant.

01 / Lifecycle

Easy entry. Deliberate decisions.

A request can return for clarification. Deferral and decline are valid outcomes; every idea does not become a build.

  1. Received

    The request has been saved. Receipt is not a promise of implementation.

  2. Needs clarification

    A reviewer asks for missing context, affected applications, users, or the desired outcome.

  3. Assessing

    The team examines feasibility, permissions, dependencies, effort, and licensing.

  4. Explore, defer, or decline

    Record a decision and its reason. Only suitable ideas proceed toward a prototype or delivery scope.

  5. Handed to delivery

    An accepted opportunity moves into a separately owned delivery backlog.

02 / Responsibilities

One register for the work.

Shared mailbox

Receives ideas and preserves the original message. A SharePoint landing page explains the service and opens an email draft.

Capture and recovery flows

Record a unique source identifier, capture the request, and reconcile missed events. Optional Teams capture is an explicit user action.

Dataverse register

Owns request state, assessment, decisions, and processing records. SharePoint holds supporting documents rather than a second copy of business state.

Reviewer Power App

Provides an assessment queue and request detail. A controlled transition action checks permissions, current state, and record version.

Notification worker

Processes durable notification jobs separately from request capture, with bounded retries and an operational review path.

Delivery handoff

Passes an approved opportunity to a separate delivery process. Capturing an idea does not authorize its implementation.

03 / Failure and recovery

Plan for the interrupted step.

Explore the proposed response to common failure scenarios.

The same message arrives twice

Enforce uniqueness on the source identifier. A repeated event resolves to the existing request instead of creating a second one. A search followed by create is insufficient under concurrency.

The request saves, but its email fails

Keep the request and retry its notification job separately. Use bounded retries, record the outcome, and send ambiguous delivery states for operational review.

Two reviewers change a decision

A transition action checks the caller, allowed state transition, and record version. Reject conflicting updates and ask the reviewer to reload current information.

A mailbox event is missed

A scheduled reconciliation compares the source mailbox with capture records using an overlap window. Missing events are replayed through the same duplicate-safe capture path.

04 / Trade-offs

Boundaries before complexity.

Dataverse is the proposed store for related records and controlled business state. A SharePoint-only pilot is an alternative to assess against licensing, access needs, and expected volume—not a second synchronized master.

Access to requests and evidence must follow agreed roles. Sensitive submissions need a private entry path. Tenant configuration, licensing, workload, ownership, and response targets must be confirmed before implementation.

Notifications are designed for retry and review; exactly-once email delivery is not promised. Financial actions and submitted automation instructions are outside this intake system.

Explore your process
Inside the project