Approvals, settings, analytics, and team governance
This is the most administrative part of the Teams dashboard and deserves its own documentation because it mixes permissions, audit logs, and irreversible actions.
Owner and Admin concentrate the workspace operation here: content approval, global rules, departments, company variables, internal announcements, and collective performance tracking.
If your team works with editorial control or area-based silos, this section determines how the extension will behave later for each employee.
Approvals for notes and links
When strict_approvals is active, what editors publish enters a pending state. The approvals inbox separates shortcut suggestions from corporate link requests, showing the proposed shortcut, audience, folder, employee instructions, and approve or reject buttons.
If the organization decides to disable that approval chain, new content can be published directly without prior review.
Corporate settings that currently live in the Teams dashboard
- Corporate branding: workspace name, logo, and primary color.
- Global policies:
strict_approvalsandstrict_isolation. - Departments: create, rename, and delete areas; when renamed, the change propagates to members, notes, and links.
- Company-wide variables for reusable tokens such as
{my_variable}. - Corporate megaphone with message, color, automatic expiration, department targeting, and optional link.
- Workspace ownership transfer from the owner's danger zone.
Analytics, adoption, and management exports
The analytics view in the Teams dashboard calculates time recovered, estimated money saved, total injections, and team adoption. It also charts evolution over 7 days, 30 days, or 1 year, highlights an employee of the month, and builds a comparative matrix by member.
The visible financial calculation starts from a reference rate of $25/hr, and CSV export for analytics reports is also available when there is already enough data in the leaderboard.
Audit log, corporate trash, and version history
The audit log stores relevant workspace movements such as approvals, imports, role changes, variable creation, or premium settings updates. This makes it possible to reconstruct what happened and who did it.
The corporate trash lets you restore or destroy deleted items, while note_versions stores previous copies of shared notes so older versions can be restored. The owner keeps the most sensitive actions, such as emptying the whole trash or purging all history.