Each tool has a Pages access setting that decides what TeamAI pages can do with it. Use it to keep one tool out of pages, or to let pages take actions through it.
Change a Tool's Pages Access
Click Tools in the sidebar and open the tool.
On the Details tab, find Pages access.
Choose an option. It saves straight away.
The Options
None: pages can't use this tool. Pages already published stop calling it.
Reads: pages can show data from the tool's read-only actions, as each viewer. This is the default.
Reads and actions: pages can also create, update or delete through this tool, as each viewer. It only covers actions the page's publisher allowed, when the workspace allows actions from pages, and each one is confirmed by the viewer.
Who Can Change It
Admins of the workspace that owns the tool, and people who can edit the tool. Pages access applies in every workspace that can use the tool, so an organization tool is set in its own workspace.
Pages Access or Live Tools?
Use Pages access to stop one tool everywhere. Use Live tools in Settings → Pages to stop all tools on one workspace's pages. See Pages Settings for Workspace Admins.
How API Tools Count
An API tool that uses GET counts as a read. POST, PUT and PATCH count as actions, and DELETE counts as an action that deletes.
When a Change Takes Effect
New requests stop right away. A page someone already has open can keep showing data it loaded for up to 5 minutes. Reloading applies the change straight away.
Frequently Asked Questions
Why can't I change Pages access?
Only admins of the tool's own workspace, or people who can edit the tool, can change it. The field says which workspace that is.
What do viewers see when a tool is set to None?
The page's Sources menu says Turned off for pages in its tool settings, and the parts that need the tool don't load.
Does Reads let a page change data?
No. With Reads, any action through this tool is refused.