I'm an Owner, but Make requires the "View team details" permission

:bullseye: What is your goal?

I want to check and correct the permission that prevents activating a scenario with an instant trigger, without changing plans or transferring ownership. Is it normal for the team dashboard to redirect to the organization dashboard on the Free plan?

:thinking: What is the problem & what have you tried?

I have an organization with a Free plan and a single team. I am the only user and appear as Owner. When trying to activate a scenario with an instant trigger, Make showed the permission error copied below.

I have already checked the following:

  • My Owner role shows all permissions enabled.
  • I can open the team settings, edit the scenario, and view its schedule.
  • When opening the team dashboard, Make redirects me to the organization dashboard.
  • Logging out and back in, even from another browser, does not change this redirection.
  • I have available credits and no active scenarios.

I don’t know if the redirection is related to the permission error. How can this be checked and resolved?

For now, I keep the scenario turned off and have removed the webhook temporarily.

:clipboard: Error messages or input/output bundles

Insufficient rights, team permission “View team details” is needed.

Hi @trujillo2026, a few things worth checking:

Team role vs. organization role. Being Owner at the organization level doesn’t always mean you have a role inside the team itself. Go to Teams → your team → Members and confirm your user is listed there with a team role (e.g. Team admin).

Webhook/scenario team mismatch. Check that the webhook and the scenario both belong to the same team. If the webhook was created under a different team, activation can fail on permissions.

Fresh test. Create a brand-new webhook and a minimal scenario (Webhook → one dummy module) in that team and try to activate it. If this works, the issue is with the old scenario/webhook; if it fails too, it’s likely an account-level issue.

Status & support. Check status.make.com, and if the fresh test fails as well, open a ticket with Make support and include the exact error text.