User roles and permissions: admin rights and who can see what

Two questions bring most teams here: how do I give a colleague the same rights I have? and how do I stop everyone from seeing everything? Both are answered on two pages.

I want to	Go to
Make someone an admin, or hand over the account	Users (my.meetergo.com/admin/team)
Decide who may create meeting pages, invite people, see other people's bookings or connect integrations	Admin Center → Organization → Permissions (my.meetergo.com/admin/permissions)

Both pages appear in the menu for company admins only, and the Permissions page can only be opened by an admin.

The roles

The Role column on the Users page shows one of these:

Badge	What it means
Owner	The account holder. One per account. Everything an administrator can do, plus being the person billing and account ownership sit with.
Administrator	Full access: Admin Center, Billing, Users, Teams, Emails, every meeting page, every booking, every integration.
Employee	The default. Manages their own booking pages, bookings, availability and calendar connections.
Partner	An external person who does not take up a seat and cannot host meetings. See Partner Users on the Free Plan.
Resource	A room, device or car, not a person. See Booking Resources.

Two further roles are assigned somewhere else and do not appear in this column:

Team admin — an administrator of one team only. See How to set a user as a team admin.
Group admin — an administrator of one group only, assigned under Groups → your group → Manage administrators.

Custom roles do not exist. You can only combine the roles above with the permission settings below.

Give a colleague the same rights you have

Open Users (my.meetergo.com/admin/team).
Find the person in the list.
Click the ⋮ menu at the end of their row.
Click Set as Admin.

The change takes effect immediately. To reverse it, use Remove Admin Rights in the same menu.

Things that surprise people here:

The menu only appears for company admins, and never on your own row. You cannot remove your own admin rights; another admin has to do it.
Partner and resource rows have no Set as Admin entry. Only regular users can become administrators.
The account owner cannot be made a non-admin. To move ownership, the current owner opens the ⋮ menu on an existing administrator and picks Transfer ownership. That entry is only shown to the owner, and only on rows that are already administrators.
Nobody is notified when their role changes, so tell them yourself.

The Permissions page

Admin Center → Organization → Permissions (my.meetergo.com/admin/permissions) holds every organisation-wide rule. Pick an option per card and click Save Changes.

Setting	Question it answers	Options	Default
Meeting types	Who can create new shared meeting types? (Co-Host & Round Robin)	All members of my organization / Admins and group admins / No one	All members
Workflows	Who can create, edit and delete workflows?	All members / Only admins and the owner	All members
Forms & Routing	Who can access and create forms and routing?	All members / Only admins and the owner	All members
Integration Permissions	Who can connect and use integrations?	All members / No one (admins only) / Custom	All members
Handoff target	Who can assign appointments to colleagues other than themselves?	All members / Admins and group admins / No one	All members
Invitations	Who can invite users to meetergo?	Admins and group admins / Admins only	Admins and group admins
Meeting & Meeting Type Visibility	Whose meetings and meeting types can non-admins view?	All members / Only team members meetings	All members
Contacts Visibility	Whose contacts can non-admins view?	All members / Only team members contacts	All members
Analytics: Admins in team filter	Should admins count in team aggregates?	Include all team members / Exclude admin users	Include all
Business card username	Who can change the username in their booking link?	All members / Only admins and the owner / Only the company owner	All members
Host availability for Microsoft connections	Should hosts with a broken Microsoft connection stay bookable?	Off, or per scope and connection type	Off

Wherever an option says Admins and group admins, team admins are included as well.

The Join Organisation card is shown with a Not available badge: joining by matching email domain is switched off across meetergo, so people can only be added by invitation.

Who can see whose bookings and calendars

By default everyone in your account can see everyone else's bookings, meeting pages and calendar view. This is the Meeting & Meeting Type Visibility → All members of my organization setting, and it is the answer to "can my colleagues see my appointments?": yes, until you change it.

To narrow it down, set it to Only team members meetings. Then a non-admin sees:

their own bookings and meeting pages, always, and
the bookings and meeting pages that belong to a team they are a member of.

Company admins keep full visibility either way, and team admins can still see the calendars of people in the teams they administer.

Only team members meetings works through teams. If nobody is assigned to a team, each person ends up seeing only their own bookings. Set your teams up first under Teams (my.meetergo.com/admin/teams).

Contacts Visibility works the same way for the contact list, and is set separately. Turning one down does not turn the other down.

Note that this is about what colleagues see inside meetergo. What meetergo reads from a connected calendar is a different question, covered in Connect your calendar.

Restricting integrations

Integration Permissions decides which services your team may connect on their own profile:

Mode	Effect
All members of my organization	Everyone can connect anything. The default.
No one (admins only)	Nobody but administrators can connect anything.
Custom	Click Configure and allow each service individually. Anything you do not tick stays blocked.

Two rules explain most "my restriction isn't working" reports:

Administrators are never restricted. The rules apply to everybody else; an admin always sees and can connect every integration.
Teams can widen the rule. A team can allow single integrations for its members. If someone belongs to several teams and any one of them allows a service, they may connect it.

When you open a colleague's profile from the Users page, the integrations are shown as they may use them, so what you see there reflects their permissions and not your own admin access.

Why can't this person edit a booking page?

Editing or deleting a meeting page (including its availability) is allowed for:

the host the page belongs to,
whoever created it,
company admins, and
the team admins of that team, for team meeting pages.

Anyone else can view it but not change it. This is separate from the Meeting types permission above, which only decides who may create new shared meeting types (Co-Host and Round Robin).

Groups vs Teams

Both exist, and they do different things:

Teams (my.meetergo.com/admin/teams) are the working unit: team booking pages, round robin, shared meeting pages, team branding, team admins and the visibility rules above. Teams need the Essentials plan or higher.
Groups (my.meetergo.com/admin/groups) are for organising and reporting on people, for example by department or location, and for group analytics. A group holds up to 30 users and up to 20 group admins.

FAQ

My co-founder shows up as a normal team member. How do we get the same rights?

Open Users, click the ⋮ menu on their row and choose Set as Admin. Both of you then have full access to every setting. Ownership of the account still sits with one person; that only matters for billing and can be moved with Transfer ownership.

Can I stop team members from seeing each other's calendars?

Yes, but you have to switch it on: set Meeting & Meeting Type Visibility to Only team members meetings on the Permissions page. Out of the box, everyone in the account can open a colleague's calendar view and bookings.

I restricted integrations, but my staff can still connect everything

Check three things: the person is not an administrator (admins bypass every integration rule), no team they belong to allows that integration, and in Custom mode the service is genuinely unticked. In Custom mode only what you explicitly allow is permitted.