What the view helps you understand
The Shadow Apps view brings together:- Application name and discovery source
- User or usage context where available
- Risk and vendor information available to the workspace
- Review or approval state
- Links to the related application and governance workflows
What counts as an unexpected application
An application may appear for review when it is discovered through a supported source but has not yet been reviewed by the workspace team. Examples include:- A vendor signal found through organization-wide mailbox discovery
- An application associated with identity-provider activity
- A SaaS or AI tool detected through browser usage
Reviewing an application
Open the application to review the available context, such as:- Where the application was discovered
- Which users or groups are associated with it, when available
- Recent usage or access context
- Risk and vendor information available in the workspace
- Related OAuth grants or findings, when available
Acting on a review
Depending on your permissions and enabled workflows, you may be able to:- Update the application’s review or approval state
- Assign an owner or add internal context
- Open a related finding or OAuth review
- Use a Pulse to confirm usage with employees
- Use a Playbook for an approved remediation workflow
Rules and notifications
If Rules and notification channels are enabled for your workspace, you can configure supported notifications for new application discoveries or review states. Delivery and timing depend on the configured channel and workspace permissions; the Shadow Apps page remains the source for reviewing the current state.Next steps
Rules
Review supported event notifications
Pulses
Verify application usage with employees
Playbooks
Follow approved remediation workflows
Apps
Review the application catalog