Skip to main content
App Approval Workflow brings your district’s app reviews into one sequential process. Administrators configure the review steps, reviewers act when it is their turn, and completed decisions remain connected to the app’s approval record.
An app’s approval status records your district’s decision. It does not automatically allow or block access to the app.

Before You Begin

Your access determines what you can do: Reviewers must be existing GoGuardian users with approval access in the applicable organization. Assigning someone to a workflow does not create an account, grant Discover access, or change their permissions. Only the eligible reviewer assigned to the active step can approve or deny that step.

Create and Activate a Workflow

A workflow contains one or more ordered steps. Each step has a name and exactly one reviewer.
  1. Open App Approval → Workflows.
  2. Select New workflow.
  3. Enter a unique Workflow name and, optionally, a Description.
  4. Enter the first step’s name.
  5. Use Search reviewers to select an eligible reviewer.
  6. Select Add step for each additional review, then arrange the steps in the required order.
  7. Review the configuration and save the workflow. Activate it when it is ready to accept requests.
  8. Verify the result: The workflow appears in the workflow list. Once active, it is available for new requests.
A workflow cannot be activated if any step is missing a name or eligible reviewer. You can have multiple active workflows. If only one is active, it is selected automatically for a new request.

Edit an Existing Workflow

Administrators can edit any saved workflow, including an active workflow, directly from the workflow list.
  1. Open App Approval → Workflows.
  2. Select the workflow’s edit icon (pencil and paper).
  3. Update its configuration and save your changes.
  4. Verify the result: Future requests use the updated configuration. Requests already submitted retain the version of the workflow they started with.
Editing a workflow does not rewrite existing requests’ original review sequence or history. You do not need to deactivate an active workflow before editing it.

Deactivate a Workflow

Deactivate a workflow when you no longer want it available for new requests.
  • You cannot deactivate a workflow while it has open requests. Complete or cancel those requests first.
  • Deactivation preserves completed request history.
  • Workflows cannot be deleted.
  • Only active workflows accept new requests. If none are active, request creation is disabled.

Submit an App Approval Request

You can start a request from:
  • App Approval
  • An app’s row in App Catalog
  • The Approval section of App Details
When starting from App Approval, search for and select the app. App Catalog and App Details already provide the app context. Complete the request form:
  1. Select an active workflow if more than one is available.
  2. Specify the proposed school and grade-level scope.
  3. Provide organizational-unit context, if applicable.
  4. Review the approval duration. The default is 1 Year, counted from final approval.
  5. Optionally add Intended use and a request comment.
  6. Submit the request.
  7. Verify the result: The request is pending review, and the first reviewer’s step is active. The app’s current approval status remains unchanged while the review is underway.

Understand the Requested Scope

Schools and Grades define approval scope. Organizational units and Intended use provide decision context; they do not override the school and grade scope. Missing scope information is not the same as an explicit Entire Organization selection. After submission, the scope is read-only. Your organization can have only one open request per app, even if the proposed workflow, scope, or requester is different.

Find Requests That Need Your Review

Open App Approval → Requests. The Waiting on you section contains requests where your assigned step is currently active. An assignment to a future step does not appear as actionable work. When there are no current assignments, the section displays Nothing is waiting on you. Use All Requests and its status filters, All, Pending Review, Approved, Not Approved, and Cancelled, to find other requests. Open a request to review its:
  • Requested scope and intended use
  • Approval duration
  • Workflow progress
  • Active and upcoming reviewers
  • Notification-delivery information
  • Available request history and Activity
The app’s current approval status and the request’s workflow progress are separate. For example, approving an intermediate step moves the review forward without yet changing the app’s approval status.

Approve or Deny a Request

Approve Your Step

  1. Open the request assigned to your active step.
  2. Review the submitted information.
  3. Select Approve Step.
  4. Add an optional comment.
  5. Confirm approval in the dialog.
  6. Verify the result: If another step remains, the request moves to its next reviewer. Approving the final step completes the request and updates the app’s standing approval record and approved scope.
Your decision is recorded against your name and cannot be edited afterward.

Deny the Request

  1. Open the request assigned to your active step.
  2. Select Deny.
  3. Enter the required reason under Reason shared with the requester.
  4. Confirm the denial.
  5. Verify the result: The request is Not Approved, and later steps are not activated.
For an initial review, denial sets the app to Not Approved. A denied re-review preserves the app’s existing standing approval, as explained in Submit a New Review for an App.
Anyone in your district with access to App Approval can read comments. Do not include confidential student information. Treat the denial reason as requester-facing.

Manage Email Notifications

Discover sends workflow emails to help reviewers know when to act and requesters know how their request ended. App approval requests emails are on by default. Each user can manage their own preference.

Review Emails Sent to Reviewers

These emails are subject to each recipient’s notification preference. Review-notification links require sign-in and open the request in the appropriate district context.

Review Emails Sent to Requesters

The requester receives an outcome email when the request reaches Approved, Not Approved, or Cancelled, subject to their email preference. For Approved and Not Approved outcomes, the email links to a read-only completed-decision receipt. The receipt preserves that request’s historical outcome and scope. Its contents depend on the recipient’s access; being the requester does not automatically grant access to internal reviewer comments or restricted attachments.

Configure Your Email Preferences

  1. In the upper-right corner of Discover, select your name.
  2. Select Account Settings.
  3. Under Email Notifications, turn App approval requests on or off.
  4. Check Unsubscribe from all emails. When this setting is on, it stops Discover emails regardless of individual notification settings.
  5. Verify the result: Changes save automatically, and the settings show your current preferences.
Turning off email notifications does not remove your review assignments or change your workflow responsibilities. Continue checking App Approval → Requests → Waiting on you for requests that need your action.

Check for Missing Emails

  • Check that App approval requests is enabled and Unsubscribe from all emails is off.
  • For review assignments, confirm that your step is currently active. An upcoming assignment does not trigger an active-step notification.
  • Check the request’s notification-delivery information. If delivery failed, an administrator can follow up outside Discover. There is no notification-retry action in the workflow.
  • Continue using the request screen to review and act. An email-delivery failure does not change the request’s state.

Reassign a Reviewer

A Super User or Discover Full Access administrator can replace the reviewer for an active or upcoming step with another eligible user.
  • Reassigning the active step immediately transfers decision access to the replacement.
  • Reassigning an upcoming step does not change the active step.
  • Completed steps cannot be reassigned.
  • An optional reason can be recorded with the reassignment.
Reassignment preserves the request’s scope and completed decisions. It does not restart the workflow.

Cancel an Open Request

A Super User or Discover Full Access administrator can cancel a request that is still open.
  1. Open the request and choose the cancellation action.
  2. In Cancel approval request?, select a reason:
    • Submitted by mistake
    • Duplicate request
    • No longer needed
    • Review could not continue
  3. Optionally add a comment.
  4. Confirm cancellation.
  5. Verify the result: The request is Cancelled. The app’s current approval status and Approval Details are unchanged, and a new request can be submitted for the app.
Completed reviews remain in request history. Cancellation cannot be undone. App Approvals Edit/View alone does not allow cancellation, including for a request you created.

Resolve a Request Administratively

A Super User or Discover Full Access administrator can conclude an in-flight request through administrative approval or denial, without waiting for the remaining reviewers. A reason is required. The record distinguishes the administrative resolution from an individual reviewer’s decision, and remaining steps are marked Skipped rather than credited as approvals or denials. Administrative resolution cannot be undone. Correcting an erroneous resolution requires a new request.

Submit a New Review for an App

You can submit a new request for an app with any approval status once it has no open request. If the app already has approved scope, its current Schools and Grades prepopulate the form. Review and change the proposed scope before submission.
A final approval replaces the app’s current approved scope. It does not automatically add the new scope to the old scope. Include the complete intended scope in the new request.
  • Starting a re-review leaves the standing approval unchanged.
  • Approving the re-review replaces the standing status and scope.
  • Denying the re-review leaves the existing approval status and Approval Details unchanged.
  • Previous requests retain their original scope, decisions, and history.
Re-review does not revoke an existing approval.

View a Completed Decision

Completed Approved and Not Approved requests have read-only historical receipts. A receipt preserves the decision and scope at completion; later edits to the app or subsequent reviews do not rewrite it. Receipt content depends on the viewer’s access. The original requester receives a limited requester-facing version, not automatic access to internal reviewer comments or restricted attachments. Final-decision emails link to the appropriate receipt when permitted by notification preferences. Receipt links from App Details are not included in this release.

Troubleshoot Approval Requests

Review Current Limitations

App Approval Workflow supports sequential reviews with one reviewer per step. It does not include conditional routing, parallel approvals, reviewer groups, supporting-document uploads within the workflow, or general teacher-facing intake.

Resources

Last modified on November 4, 2026