When a user asks their AI assistant to delete something, make a bulk change or take one of a few other high-impact actions, nothing is written until the user approves it in their browser. Reads, and creates or updates of a single record, run straight away.
Which Changes Wait for Approval
| Risk tier | Changes that wait |
|---|---|
| Destructive | Deleting a Task, Task Group, Checklist Group, Checklist Item, Dependency, Time Entry, Time Away, Attribute Type, Attribute, Attribute Assignment or Baseline, or removing a Holiday from a Business Schedule |
| Bulk | Creating or updating many Projects, Tasks, Task Groups, Checklist Groups or Checklist Items in one request |
| Elevated | Cloning a Project, stitching a template Project or Task Group into a Project, importing a template, and archiving or unarchiving a template |
How Approval Works
- The assistant gives the user a link to approve or reject the change, usually with a summary of what will change.
- Only the user whose connection queued the request can see or approve it. Other users can't, the assistant can't, and neither can you, as an admin.
- When the user approves, the change runs as that user, with their Salesforce permissions. When they reject it, nothing is written.
- If nobody decides within 24 hours, the request expires and nothing is written.
When a Record Changes Before Approval
If a record the request would change is edited after the request is queued, or the user can no longer see it, nothing is written when the user approves, so a teammate's edit isn't overwritten. The assistant can then queue a fresh request.
Good to Know
- A delete or bulk change the assistant reported that hasn't shown up in TaskRay is most likely still waiting for approval.
- Asking for the same change while the first is waiting doesn't queue a second one.
- The user can ask their assistant to check on a request it queued, such as "Did my delete of the Kickoff call task go through?" The assistant can't see anyone else's requests.
- An approved request still unfinished 24 hours after it was queued expires, and some of its records may already have been written. Until then, the user can retry it from the approval page.
Frequently Asked Questions
Q. Can I approve a waiting request for a user who's away?
Great question! No. Only the user whose connection queued it can approve it, and after 24 hours it expires with nothing written.
Where to Go Next
- TaskRay MCP Tool Reference: Overview: the risk tiers, and which tools a user gets.
- TaskRay MCP Tool Reference: Responses and Error Codes: what an error means, and who can fix it.
Have a question this reference doesn't answer? Not to worry, our Support Team is ready to help! Contact TaskRay Support with what the user asked their assistant to do, the exact error text, and whether the org is production or sandbox.