Who can manage triggers?

An agent Owner manages every user-configurable trigger on it. Users can always view, deactivate, and delete their own triggers while they retain access to the agent. When Create triggers is Allow, Users can also create, edit, and activate their own triggers. This covers independent scheduled, app, webhook, and AI-created custom triggers. Shared template copies have a separate exception: people who can use the agent can turn on an available copy and change its offered personal settings without Create triggers permission.

​

Who can do what

Every trigger belongs to its creator and uses its configured accounts. Shared copies can use subscriber-selected personal accounts or permitted inherited team accounts. Team membership doesn’t let someone manage other people’s copies.

​

What can I do with a shared trigger?

If you can use the agent, you can turn on an available shared trigger, choose the required accounts or timezone, and pause or delete your own copy. The Create triggers setting doesn’t gate these copy-specific actions. It still gates creating your own independent triggers. The template controls the shared prompt and configuration, not its subscribers. To start sharing an original trigger, you must be its creator and have permission to manage triggers on the agent. See Agent triggers for the full setup and lifecycle.

​

Turning trigger creation off

Set Create triggers to Don’t allow and Gumloop asks what to do with the triggers Users already have:

• Keep running: they keep firing. Users can’t create, edit, or activate independent triggers, but can still view, deactivate, and delete their own. Shared-copy actions follow the exception above.
• Disable them: they stop firing.

Owners can still see and manage those triggers from the Triggers tab either way. See Let a User create triggers. Turning Create triggers off isn’t the same as removing access to the agent. Owner-owned triggers keep running as before. Allowing creation again doesn’t automatically reactivate disabled triggers. If a trigger’s creator loses all access to the agent, Gumloop removes their triggers. Removing one share doesn’t remove them if another grant still provides access. Moving the agent to another team can also remove triggers. Existing Organization access carries over when it matches the destination team’s organization. Otherwise, access resets to the new team. Creators who lose all access have their triggers deleted. Gumloop can also delete triggers that depend on the old team’s connectors. See Move their agents to a team.

​

What you see in the Triggers tab

Your triggers appear under Mine. Owners and Org Admins can also see other people’s triggers under Team.

​

If the agent can’t change a trigger for you

During a task, the agent can only work with triggers you own, even if you are an Owner. To manage someone else’s trigger, open the Triggers tab. The agent can’t update a shared copy’s configuration. Use Change settings for its offered personal settings.

​

FAQ

​

Related