How approvals and pending state work
In Teams, sharing does not always mean publishing immediately: it depends on the role and the workspace configuration.
The extension supports a flow in which certain items created by users such as editor stay in pending state until an admin or owner approves them.
This especially applies to content that must remain consistent across the team, such as shared snippets, operational notes, and internal links.
Typical flow
The user creates or edits content in the team workspace
It can be a note, a shared snippet, or an internal link.
The extension marks the content as pending if the role or policy requires it
In that state the resource exists, but it is not yet published as final material for everyone.
Admin or Owner reviews and approves
Once approved, the content becomes available according to the team's visibility settings.
How this intersects with departments
Even after approval, content can still be limited to a specific department if the organization uses internal segmentation. The value all is used for company-wide content.
That is why approval does not guarantee universal visibility: final publishing still respects department and isolation rules.