How approvals and pending state work
In Teams, sharing does not always mean publishing right away: it depends on the role of the person saving and on the team settings.
On this page · 10 sections
When an editor saves a snippet, a note or a link to the team vault, that content is not published straight away: it stays pending and shows up in the approval inbox of the web dashboard. An administrator or the owner decides whether to approve or reject it.
This check keeps a text with mistakes or a wrong link from reaching the whole team without anyone reviewing it.
Who submits and who approves
| Role | When saving to the team vault | Can approve or reject? |
|---|---|---|
Owner | When saving to the team vault Published right away. | Can approve or reject? Yes. |
Administrator | When saving to the team vault Published right away. | Can approve or reject? Yes. |
Editor | When saving to the team vault Stays pending review. The save button changes to “Send for Review”. | Can approve or reject? No. |
Viewer | When saving to the team vault Cannot create or submit content to the team: only uses what is already published. | Can approve or reject? No. |
Everything you save to your personal vault is always saved instantly, with no review, whatever your role. Approvals only apply to content saved to the team vault.
2Typical flow
The editor creates or changes content in the team vault
They can do it from the popup, the Notebook or the web dashboard. It can be a snippet with a shortcut, a note or a link.
On save, the content stays pending
In the extension, the item shows a “REVIEW” label and, when you open it, a yellow “Pending Approval” notice. In the web dashboard you see the message “Suggestion sent for review.”
The request reaches the approval inbox
Administrators and the owner see the “Approvals” section in the team dashboard, with a count of pending items. The dashboard overview also shows the “Pending Requests” card.
An administrator or the owner approves or rejects
If approved, the content moves to the Master Vault and is sent to the team's extensions on the next sync. If rejected, the suggestion is deleted.
3How to review the approval inbox
Open the inbox
From the extension: open the menu, go to “Business Panel” and click “Approvals”. You can also go to the team's web dashboard and choose “Approvals” in the side menu. This option only appears for administrators and the owner.
Review each snippet or note
Under “Shortcuts and Snippets” you see the title, the proposed shortcut (or “None” if it has none) and a preview of the content.
Review each link
Under “Corporate Links Requests” you see the name, the address (you can open it to check it), the instructions the employee wrote, the audience, the command and the folder.
Click “Approve” or “Reject”
“Reject” asks for confirmation before deleting the suggestion. Every approval and every rejection is recorded in the dashboard's “Audit Log” section, along with who did it.
4Edits and delete requests
- If an editor changes a team snippet or note and saves the change from the extension, the item goes back to pending review.
- In the web dashboard, an editor can create new content for the team but cannot edit items that already exist: they see them in read-only mode.
- In the popup's link list, an editor can only copy or open team links; the edit and delete buttons appear for administrators and the owner.
- In the Notebook, if an editor tries to delete a team note, the note is not deleted: it stays pending with “[SOLICITUD BORRADO]” in front of the title, and the notice “Request sent. The Owner must approve this action.” appears.
Tip
When handling a delete request, keep in mind that “Reject” deletes the item permanently, which is what the editor asked for. If you decide to keep it, approve it and remove “[SOLICITUD BORRADO]” from the title.
5Turning approvals on or off
In the team dashboard, under “Roles & Permissions”, there is a switch called “Chain of Command (Approval Workflow)”. It is on by default. If you turn it off, whatever editors save from the web dashboard is published right away, without going through the inbox. Administrators and the owner can change it.
Important: this switch applies to what is saved from the web dashboard. In the extension, whatever an editor saves to the team vault always stays pending review.
6How this intersects with departments
Approving an item does not automatically make it visible to the whole company. Every item has an audience: a specific department or “Entire Company”. In the inbox you can see each link's audience before approving it.
If the owner turns on isolation between departments, each employee only receives content from their own department plus content marked for the entire company. Administrators and the owner see all departments.
Common problems and fixes
| What happens | Why | What to do |
|---|---|---|
My snippet has the “REVIEW” label | Why You are an editor and saved it to the team vault. | What to do Wait for an administrator or the owner to approve it. It has not been lost. |
I edited an approved snippet and it went back to review | Why Every change an editor makes to team content goes through review again. | What to do Let an administrator know so they can review the change. |
I don't see the “Approvals” section | Why Only administrators and the owner can see it. | What to do Ask the owner to change your role if you need to review content. |
My suggestion disappeared | Why It was probably rejected: rejecting deletes it. | What to do Check with your administrator and submit it again with the fixes. |
Nobody can create or edit team content | Why If the team has a payment problem, the extension switches to read-only for everyone in the team vault. | What to do The owner needs to check billing. The personal vault keeps working. |
8What the approval system does not do
- It does not review your personal vault: everything there is saved without approval.
- It does not let you comment or ask for changes from the inbox: there is only “Approve” and “Reject”.
- It does not keep a copy of rejected suggestions: rejecting deletes them.
- It does not notify the editor when their content is approved or rejected; the decision is recorded in the “Audit Log”, which administrators and the owner can see.
Warning
Deleting or rejecting shared content can affect the whole team, and a rejected suggestion cannot be recovered. Before doing it, confirm whether you are in your personal space or in the company vault.
10Frequently asked questions
What happens to a rejected suggestion?
It is deleted permanently after you confirm. It does not go to the trash, so the editor would have to create it again.
When does everyone else get the approved content?
Once approved, the content moves to the Master Vault and the team's extensions download it on their next sync.
Can I turn approvals off?
From “Roles & Permissions” you can turn off the approval workflow for content saved in the web dashboard. Whatever an editor saves to the team vault from the extension still stays pending.
Where can I see who approved or rejected something?
In the “Audit Log” section of the team dashboard, where every approval and rejection is recorded with the account that made it.