Understanding Compliance Badges
When browsing the tool catalog, you will notice colored badges and pills on each tool card. These visual indicators give you an at-a-glance view of a tool's compliance posture without needing to open the detail page.
Review Status Badges
Each tool displays one of two review status badges:
- Reviewed (green badge) -- All key compliance fields have been filled in and the tool has been assessed by an Admin or Owner. A green badge signals that the tool's risk profile is documented and up to date.
- Needs Review (yellow badge) -- One or more compliance fields are missing or the tool has not been formally reviewed. A yellow badge means the tool requires attention before it should be considered fully vetted.
What triggers "Needs Review"?
A tool is marked as Needs Review when any of the following fields are empty or unset:
- Data Classification
- SOC 2 Status
- DPA Status
- Risk Level
Once all four fields are completed, the badge automatically changes to Reviewed.
Data Classification Color Pills
The data classification field is shown as a small colored pill on the tool card:
- Public -- displayed in gray to indicate low sensitivity.
- Internal -- displayed in blue to indicate standard business data.
- Confidential -- displayed in orange to signal sensitive data requiring care.
- Restricted -- displayed in red to highlight the highest sensitivity level.
These colors are consistent throughout the application so you can quickly scan the catalog and identify tools handling sensitive data.
How to Use Badges Effectively
- Filter by review status to find tools that still need compliance data filled in.
- When evaluating whether to request access to a tool, check the badge and classification pill first. A Reviewed tool with a low classification is generally safe to use, while a Needs Review tool with a Restricted classification warrants caution.
- Admins should periodically review the catalog and aim to move all tools from yellow to green status by completing their compliance fields.
For a detailed explanation of each compliance field, see Compliance Fields.