Lifecycle of a Business

What is the Lifecycle of a Business?

There are multiple states that a Business goes through from creation to approval. Middesk helps track these states, and always provides auditable records of how a report has changed and progressed over time.

Middesk customers are able to build unique programmatic workflows based on the progression of a report through the Lifecycle. They do so by relying on the status field returned in the Business object.

Status of a Business

All Middesk Businesses go through the same Lifecycle after they have been created. These stages can be tracked either through the Middesk Dashboard or the Middesk API by examining the status field within JSON response returned by the Retrieve a Business endpoint.

The following are the various statuses that a Business could be in:

StatusDescription
openThe request for the Business has been received, but Middesk has not yet kicked off the searches for this Business.
pendingMiddesk has kicked off searches for this Business, but has not yet completed them.
in_auditMiddesk is required to Audit and ensure the quality of this Business.
in_reviewThe Business is ready to be reviewed by the Middesk client. Action items for the client are listed in the Review Resource.
approvedThe Middesk client moves the Business to an approved status.
rejectedThe Middesk client moves the Business to a rejected status.

When the status of a Business is changed to in_review, Middesk may have a list of action items for you to go through. These action items will be provided in the [Review] Resource, which we will learn more about in the next section.

Middesk designates a User on your Account as the assignee for the Business. The assignee is the user who created the Business in the dashboard. If the Business was created via API or Batch CSV, the assignee will be your account's default assignee if set and otherwise the first account admin user. You can update your default assignee on the Team settings page. The assignee will receive an email when the Business moves to in_review, unless the User in question has disabled notifications in their User settings.Through the Middesk dashboard and API, the Business can also be assigned the "approved" or "rejected" labels, which your team can use to apply a compliance/risk decision.

Status of a Business with Policies

If Policies is enabled, Middesk won't send the business.updated webhook when the business enters the in_review stage. Instead, Middesk will send out a business.updated webhook only after evaluating the Policy ruleset with the relevant result.

The following are the various statuses that a Business could be in with Policies enabled:

StatusDescription
openThe request for the Business has been received, but Middesk has not yet kicked off the searches for this Business.
pendingMiddesk has kicked off searches for this Business, but has not yet completed them.
in_auditMiddesk is required to Audit and ensure the quality of this Business.
in_reviewBased on the set Policies, this Business' attributes don't match either the approved or rejected criteria.
approvedBased on the applied Policies, this Business has an approved status based on the returned attributes.
rejectedBased on the applied Policies, this Business has a rejected status based on the returned attributes.

What’s Next