Skip to main content
Your team signs in to Studio and Triggr Core with one account; members, roles and user groups are shared by both apps.

Your team and permissions: invitations, roles, a group of approvers, and removing someone safely (1:29).

​
Invite your team

1

Open Members

Click your organisation’s name at the top right, then Manage > Members.
The Organization dialog's Members tab with Members 4, Invitations 1 and Requests 0 tabs, a Search box, an Invite button, and rows for Alex Morgan as Admin, Sam Taylor as Approver, and Priya Shah and Chris Lee as Member.
2

Send invitations

Click Invite, enter email addresses separated by spaces or commas, choose the Role and click Send invitations.
The Invite new members form with jordan.blake@yourmsp.com entered, the Role list open on Approver, Admin and Member, and Cancel and Send invitations buttons.
3

Let them accept

Each person follows the emailed link, then signs in at app.triggr-app.com.
To change someone’s role later, pick it from the Role list on their row.

​
Roles

Studio has three roles. You can’t add your own or change what a role includes. Whatever their role, anyone can answer an approval sent to their email address or to a user group they’re in, and complete tasks on Manual Steps.
Admin for the people who build, Approver for engineers who follow requests and runs, Member for people who only use your internal apps and approve.

​
Group your approvers

A user group lets anyone in it answer an approval, so requests don’t wait for one person. Find them in Settings > User Groups.
1

Create a group

Click New Group, enter the Name and Description, and click Create Group.
The Create New User Group dialog with Name Service Desk and Description First-line engineers who approve new starter and leaver requests, and Cancel and Create Group buttons.
2

Add people

Click Members on the group’s row, then Add Member, point to a person and click Add. The dialog closes after each one, so click Add Member again for the next.
The Add Member dialog with a Search users box and Chris Lee, Jordan Blake and Morgan Reid listed, with an Add button showing on Chris Lee's row.
The Service Desk group page with Refresh, Edit and Delete buttons, a Group Information card showing 3 members, and a Members card listing Alex Morgan, Sam Taylor and Priya Shah, each with Remove, and an Add Member button.
3

Send approvals to it

In a workflow, set a Human In The Loop or Approval With Logging step’s Approval Type to Group and choose the User Group.
The Human In The Loop step panel with Approval Type Group, User Group Service Desk, a Subject and Body built from ctx.params templates, and Response Type Approval.
Group approvals don’t send an email: members find them on Approvals, and the first answer counts. See Approvals and manual steps.

​
Remove someone

1

Take them out of your user groups

Open each group in Settings > User Groups and click Remove on their row. Do this first: removing someone from the organisation leaves them in every group, listed as Unknown.
2

Remove them from the organisation

On Members, click … on their row, then Remove member. They lose access to Studio and Triggr Core at once.
The Members table with the actions menu open on Chris Lee's row, showing Remove member.
3

Revoke their MCP tokens

Removing someone doesn’t stop their tokens. Go to Settings > MCP, click Revoke on each one, then Revoke Token; the list doesn’t show owners, so name tokens after the person who uses them.
The MCP Access Tokens page listing Priya Shah – Claude Code and Chris Lee – Cursor as Active with Revoke buttons, and Sam Taylor – Codex as Revoked.
4

Tidy up

Revoke any API Keys they knew (keys belong to the organisation, not a person).

​
Partner Access

When a portal provider that partners with Triggr asks to embed your forms, the request appears in Settings > Partner Access (admins only). Click Approve or Deny: approving lets the partner show your Microsoft-authenticated forms in its own portal and sign your clients’ users in, for every client you manage. Revoke on an Active row stops that at once.
The Partner Access page explaining that approved partners can embed your Microsoft-authenticated forms in their own portals, with a table showing Example Portal Co as Active, requested Sep 5, 2026 and approved Sep 16, 2026, with a Revoke button.

​
FAQ

Member sees only Internal Apps and the Dashboard; Approver adds Clients, Forms and Workflows; Integrations, Settings and the New buttons need Admin.
Group approvals don’t email anyone. Check they’re in the group the step names, then look on Approvals.
A denied or revoked request stays revoked, even if the partner asks again. Contact Triggr support.