What Happens to Existing Triggers When I Change an Agent Collaborator's Role?

Last updated: May 29, 2026

Existing triggers keep firing as long as the user who created them still has at least Use Only access to the agent (which includes read). Downgrading Editor → Viewer or Editor → Use Only does not break their triggers. Triggers are deleted automatically only when the user loses access entirely.

What Determines if a Trigger Keeps Firing

Every time a trigger is about to fire, Gumloop checks one thing on the trigger's creator: do they still have read access to the agent?

Read access is included in every sharing role:

Creator's current role	Has read access?	Existing triggers continue?
Owner	Yes	Yes
Editor	Yes	Yes
Viewer	Yes	Yes
Use Only	Yes	Yes
No access (removed)	No	No — deleted automatically

This applies to all trigger types: scheduled, integration (Gmail, Slack, Sheets, etc.), AI triggers, email-to-agent, and any other inbound trigger.

The trigger continues running under the original creator's identity — credits, API quotas, and credentials still come from their account, exactly as before the role change.

What the Downgraded User Can No Longer Do

Creating, editing, and deleting triggers requires Editor or Owner access. After a downgrade to Viewer or Use Only, the user can no longer:

Create new triggers on the agent
Pause, edit, or rename existing triggers they created
Delete their own triggers

If they need to change or stop a trigger, an Editor or Owner on the agent has to do it for them — or bump their role back to Editor temporarily.

When Triggers Actually Stop Firing

A trigger is deleted automatically the moment the creator loses read access. The most common ways that happens:

You remove them from the share dialog entirely. The trigger is deleted in the same transaction that revokes access — there's no grace period.
General Access is narrowed (for example, from Organization to Restricted) and they were relying on it without a direct grant. See What Happens When I Change General Access on a Shared Resource?
They get removed from the team/workspace the agent lives in and have no direct individual share.
The agent itself is deleted. All triggers on it are deactivated.
An Editor or Owner manually disables or deletes the trigger from the agent's Triggers page.

What About Moving the Agent to Another Team?

Moving an agent to a different team workspace re-evaluates every trigger:

If the trigger's creator still has access in the destination team, the trigger is relocated and keeps firing on its schedule.
If the trigger uses workspace-scoped credentials (team apps) that don't exist in the destination team, that trigger is deleted because the credential can't be resolved.
Scheduled triggers have their Cloud Scheduler job re-created under the new project.

If you move an agent and notice a trigger went missing, the most likely cause is a team-credential mismatch. Re-add the credential in the destination team and recreate the trigger.

Related Docs

Still Need Help?

If this didn't resolve your issue, reach out to support at support@gumloop.com.