Approve what your team wants to share

For managers and admins. Find pending Skills, read the exact version somebody submitted, and either approve it or send it back with feedback.

Members can build and privately run whatever they want. What they cannot do is widen it. The moment a member wants their work seen by their department or by the company, it comes to you.

A manager approves sharing into their own department.
An admin approves sharing into a department or across the whole company.

Find what is waiting

Open Skills in the left navigation.
Set the filter to Needs review. Pending items also sort to the top on their own, and each carries a Needs review badge.
Open one.

Routines arrive here too. When somebody shares a Routine, the product mints a Skill copy of its instructions and that copy is what you review, so everything pending is in one place.

Read it before you approve

You are approving one exact version, not a living document. Read the instructions and the success criteria the author wrote, and ask the practical questions:

Does it name the right tools, channels and audiences for the people who will run it?
Does it say clearly enough what "done" looks like that somebody else can rely on the result?
Does anything in the text contain information that should not travel further, such as a customer name or an internal figure?

Nothing about approving grants access to the author's private setup. Whoever adds this later runs it on their own connected accounts, under their own permissions.

Approve or send it back

Choose Approve and share, then confirm the audience that was requested. That version becomes visible to the department or the company and, at company scope, becomes a Marketplace listing.
To decline, write a note in the review feedback box and choose Send feedback. The author sees your note on the Skill and can fix it and resubmit. Feedback is required, so nobody gets a silent rejection.

If the author edits the Skill while it is waiting, the pending request is dropped, because the version you were asked to approve no longer exists. They need to submit again. This is the point: you can never approve one version and publish another.

A worked example

A member on the Marketing team submits Weekly competitor scan to the whole company. You open it, see it names a specific Notion database that only Marketing can reach, and decide it is not company material as written.

Write: "Great Routine. Point it at a page the whole company can open, or resubmit this to Marketing only." Choose Send feedback. They resubmit to their department, their manager approves, and it is live for the people it actually suits.

What to check

Approve and share is not there. The item is not pending, or it is not yours to govern. A manager cannot approve a request aimed at another department or at the whole company.
You cannot find a submission you were told about. Check that you are on Skills, not Routines, and that the Needs review filter is on.
Send feedback is disabled. The note is empty. Type something first.
The author says it vanished. They edited it after submitting. Ask them to submit the new version.