Agency staff and permissions

Owner and staff, scoping a member to certain client locations, and the things staff deliberately cannot touch.

Last updated October 14, 2026

There are 2 teams and this is the smaller one. Console staff work across clients; the moderators and managers who answer reviews inside a single location are a separate list, managed inside that location under Team.

Inviting somebody here once beats adding the same person to 6 locations by hand.

What you need: the agency owner. Staff cannot invite or remove other staff.

The 2 roles

Owner owns the account itself: what we bill you, what your clients pay, and the name on the app. There is exactly 1, and the owner can buy credits, change the commit, set retail prices and allocations, edit branding and the domain, invite and remove staff, and delete the account. The owner cannot be removed from this screen. Hand the account over first.

Staff run the work. They can open and run the locations you give them, create locations and set allocations, suspend and reactivate a location, and invite members inside a location. They cannot see or change billing and credits, cannot change branding or the domain, and cannot invite or remove console staff.

A person who runs six client inboxes every day does not need to see your margins to do it.

Suggested image Screenshot of /dashboard/team: the Console staff table with four rows showing avatar and email, the Owner and Staff role badges, location access reading a named client on one row and two named locations on another, and an Invited status with the time it was sent.

Inviting somebody

  1. Press Invite staff.
  2. Add their name and work email.
  3. Pick the role. The can and cannot list for it is printed under the picker, so nobody is guessing what they are handing out.
  4. Choose Location access: tick the locations and clients they work on. Staff with nothing ticked reach no location.
  5. Send it.
Suggested image Screenshot of the Invite staff modal: name and work email fields, the role select set to Staff, the can and cannot list for that role, and the Location access pickers with a client and three locations ticked.

They set their own password from the email and land on this panel. The invite expires in 7 days, and Resend invite on the row issues a new link, which stops the previous one working.

Scoping to certain clients

A client you tick includes all of that client's locations, also ones created after today. That is what you want for a member of staff who covers a whole client.

Specific locations is the answer for a freelancer or a client-facing account manager: they enter only the locations you ticked and see nothing of the others. Their row shows the names, so the table answers "what can this person reach" without opening anything.

Console access is not the same as location membership. Adding someone here does not put them on any location's own team, and a moderator inside one location never sees this panel or learns it exists.

Removing somebody

Remove from account ends their session immediately and stops the panel loading for them, on every location at once. Nothing they did is undone and the locations themselves are untouched.

Handing the account over

Ownership is transferred rather than invited, and the staff table will not let you remove the owner while they still hold the account. Invite the person as staff first and let them sign in, then hand the account over before removing anybody. There is 1 owner at a time. If the transfer has to happen today, email support@reviewcomet.com and we will move it.

Was this helpful?

Still stuck? Send us the profile and the comment you are looking at and we will answer with the fix rather than a link back here.

Contact ReviewComet support