Official Wrike documentation references
Source: deck slides 19–26 (Appendix) · Official Wrike documentation | Pilot capability references
In the deck, each article title is a hyperlink ("Article — click to open"). The links were not available in the text this page was built from, so articles are listed by title. Add the URLs in the Link column as they are collected.
Agent governance and permissions#
1 of 2 · Agent setup and control over who can create or manage agents (slide 20)#
| Article | What this documents for the Pilot | Link |
|---|
| About AI Agents | Space-level operation, Space-admin prerequisites, accessible context and the trigger/action execution model. | |
| How to Create an AI Agent | Configure scope, triggers and actions, test the setup, and save an agent without active scope. Saving a configuration is not independent approval. | |
| Build an AI Agent in Chat | Build or edit an agent in conversation and review its setup before saving and turning it on. This is builder review, not a separate approver's sign-off. | |
| Control AI Permissions by User Type | Restrict agent creation and management by user type. Important: these permissions do not stop users from appointing existing agents to locations. | |
2 of 2 · Account permissions, location permissions and AI enablement (slide 21)#
| Article | What this documents for the Pilot | Link |
|---|
| User Types in Wrike | Manage account-level feature permissions, including AI and API-app administration. Distinguishes user types, admin permissions and item access roles. | |
| Space Admin Rights | Explains who can manage Space settings, membership and configuration. Supports the explanation of governance responsibilities and setup rights. | |
| Access Roles in Wrike | Control what users can do in shared Spaces, folders and projects. Covers inherited access and role limits relevant to least-privilege configuration. | |
| Generative AI | Account-owner enablement and disablement, AI terms acceptance and account-level governance. This is broader than disabling one individual agent. | |
Agent scope, actions and testing#
1 of 2 · Where agents act, when they run and what they can do (slide 22)#
| Article | What this documents for the Pilot | Link |
|---|
| Appoint an AI Agent to a Location | Appoint an agent to a task, folder or project. Explains appointed scope and existing permissions. For newer Active locations setup, also check the current creation guide. | |
| AI Agent Triggers Reference | Scheduled and event-based execution, trigger scope, item versus subitem behaviour, and the context an agent can read. | |
| AI Agent Actions Reference | Supported actions, filters, targets and execution order. Agents can manage work-item approval flows; this does not mean the agent itself has an activation-approval gate. | |
2 of 2 · Validate behaviour and understand the limits before Pilot use (slide 23)#
| Article | What this documents for the Pilot | Link |
|---|
| Test AI Agents in the Playground | Preview reasoning and responses on sample items without changing live work. Supports testing before deployment, not approval of each live transaction. | |
| AI Agent Limitations and Troubleshooting | Documents unsupported deletion, assigned-scope boundaries, data-access restrictions, execution limits and troubleshooting. Some limits apply to specific actions. | |
| Write Effective AI Agent Prompts | Use clear instructions, examples and fallback behaviour; start small and test before deployment. Good prompts are an operating practice, not guaranteed injection protection. | |
Monitoring, audit and attribution#
Registry visibility, action records and attribution for AI Agents and MCP (slide 24).
| Article | What this documents for the Pilot | Link |
|---|
| Monitor AI Agent Activity | Space-level agent overview: status, locations, creator and changes. Detailed logs show actions, affected items, timestamps, outcomes and reasoning. | |
| Activity Report in Wrike | Account activity and audit reporting. Actor type distinguishes UI, Wrike agents, Automation, MCP and API. Logging does not by itself establish immutability. | |
| Creating Activity Reports | How authorised admins generate and download reports, filtering by users, dates, operations, objects and IP addresses. | |
| Icons to Identify Updates Made by Agents, API, and MCP | Attribution in the work-item stream and Inbox, with visibility controls. Some API/MCP updates omit agent identity; attribution is not shown in email or print. | |
MCP, authentication and access#
Help Center guidance, with current Developer Portal setup as a technical companion (slide 25).
| Article | What this documents for the Pilot | Link |
|---|
| Wrike API | OAuth-app registration, user-permission inheritance, permanent-token creation/revocation and the API App Activity panel. Does not validate WPP's middleware configuration. | |
| Wrike Model Context Protocol (MCP) | Architecture, authentication, access boundaries and security FAQs. Caution: this article includes legacy SSE endpoint and attribution details; pair it with current v2 documentation. | |
Wrike MCP Server Overview
Developer Portal — current v2 setup | Current endpoint, connection setup, authentication and permission model. Use this technical companion for MCP v2 setup rather than copying legacy endpoints from the Help Center. | |
Understanding AI usage#
Existing visibility and usage features (slide 26).
| Article | What this documents for the Pilot | Link |
|---|
| Wrike AI Usage reports | Explains AI Essentials and AI Elite, action consumption, plan allowances, usage reporting and exports. Check WPP's subscription before applying plan-specific features. | |
Discussion log#
| Date | Topic | Decision / outcome | Owner |
|---|
| | | |