Teams

Updated August 24, 2026

A team is a bundle of permissions, a scope of locations, and a list of members. Everything a person can do in Pluspoint comes from the teams they belong to. Every messaging channel is owned by exactly one team, and that ownership decides who sees which conversations in the Inbox. Use the Teams tab to model your org: one team per region, per brand, per function, or all three.

Before you start

Requires Account Settings = Full on one of your teams, or being the account owner.

A team needs at least one member, so have the people in the account first. See Users and permissions.

Brand-based scope needs at least one brand. The whole Scope block is only offered when the account has more than one location.

Because managing teams already requires Account Settings = Full, you can grant a team any permission and any scope, including ones your own teams do not have.

Where to find it

Select Settings in the left sidebar, then the Teams tab. Direct link: https://app.pluspoint.io/account-settings/teams.

What a team carries

Part	What it does
Permissions	A tier — None, Restricted or Full — for each of the ten modules
Scope	Which locations the team’s scoped permissions apply to: global, selected brands, or selected locations
Members	The users who inherit all of the above. At least one is required
Channels	The messaging channels the team owns, assigned on the Channels tab

A user in several teams gets the union of their access, so give people narrow teams and combine rather than building one enormous team per person.

Every account starts with two teams:

Admins — every module at Full, including Account Settings = Full, with global scope. The account owner is its first member.
Users — a sensible default set of Restricted tiers on Contacts, Locations, Reviews, Messaging, Surveys, Campaigns and Coupons, with global scope and no members.

Create a team

Select Create team below the table.
Enter a Team name. It is required and capped at 80 characters.
On the Members sub-tab, use Add member to search the account’s users and add them.
Switch to the Permissions sub-tab and set a tier for each module.
Set the Scope if the block is shown.
Select Save.

You can also create a team without leaving the user form. When you add a user, the Teams dropdown offers Create team if you have Account Settings = Full.

Set the permissions

The full matrix of what every tier allows is in Users and permissions.

A new team starts with every module at None, except Contacts, which starts at Restricted because it has no None tier.

Note Contacts access is always granted. If you somehow save a team with no contacts permission, the server adds Contacts = Restricted back.

Modules marked with a Global chip — Contacts, Messaging, Campaigns and Account Settings — always cover the whole account and ignore the scope you set below.

Set the scope

The Scope block is only shown when it can make a difference: it is hidden if the account has a single location, or if no scoped module — Locations, Reviews, Social, Web pages, Surveys or Coupons — is set above None. In either case the team is saved with global scope.

Option	What it needs	Effect
Global access level	Nothing	Scoped permissions cover every location in the account
Brand-based access level	At least one brand selected under Brands	Scoped permissions cover the locations inside those brands
Location-based access level	At least one location selected under Locations	Scoped permissions cover only those locations

Duplicate a team

Select the duplicate icon on a row. Pluspoint immediately creates a copy with the same permissions, scope, scoped brands or locations and members. There is no confirmation step, so open the new team and rename it afterwards.

Teams, channels and Inbox visibility

In the Inbox, scope does not decide who sees a conversation — team ownership does.

Every channel is assigned to exactly one owning Team when it is created, and that field is required.
The dropdown only offers teams with a Messaging tier of Restricted or Full.
A conversation belongs to the team that owned the channel it arrived on. It stays with that team until someone uses Move to team in the Inbox, or until the channel itself is reassigned.
A user sees a conversation if one of their teams owns it, or if they were explicitly added to the conversation as a collaborator.
Collaborator access is read-and-notes only. It does not confer the team-scoped actions, and it does not count towards analytics.
The account owner and anyone with Account Settings = Full see every conversation in the account.

Two consequences follow for teams:

A team that owns channels cannot have its Messaging access removed. Setting Messaging to None returns Cannot remove messaging access from a team that owns channels. Reassign its channels first. Removing Messaging access from a team that owns nothing succeeds, and releases that team’s conversations back to each channel’s default team.
A team that owns channels cannot be deleted until those channels are reassigned.

To change who handles a channel, open Settings → Channels, edit the channel and pick a different Team. See Channels.

Delete a team

Select the delete icon on the row.
Confirm at Confirm deletion.

Deletion is refused in two cases:

Blocker	What you see
It is the account’s last team	A generic Couldn’t delete — an account must always have at least one team
The team owns one or more channels	This team owns channels. Reassign its channels to another team first.

Once a team is gone, conversations that belonged to it are visible only to the account owner and to users with Account Settings = Full. Open conversations assigned to its former members return to the unassigned queue. If you want those conversations to stay with a working team, reassign the team’s channels before you delete it.

Troubleshooting

Symptom	Cause	Fix
The Teams tab is missing	You do not have Account Settings = Full	Ask the account owner or an admin — the tab is hidden and the URL redirects for everyone else
The Scope block is nowhere to be seen	The account has one location, or no scoped module is above None	Give the team a scoped permission such as Locations or Reviews; the block appears once the account has more than one location
Saving fails with a generic Couldn’t create or Couldn’t edit	A required brand or location list is empty, or a selected brand, location or member no longer exists	Complete the Brands or Locations selection, then reopen the modal so it reloads the account’s current brands, locations and users
Cannot remove messaging access from a team that owns channels. Reassign its channels first.	The team owns channels	Reassign those channels to another team on the Channels tab, then lower the Messaging tier
This team owns channels. Reassign its channels to another team first.	The team you are deleting owns channels	Reassign the channels first
A team does not appear in a channel’s Team dropdown	That team’s Messaging tier is None	Set Messaging to Restricted or Full on the team
This team has no messaging access. Choose a team with messaging permissions.	The submitted team cannot handle messaging	Pick a team with Messaging access, or raise that team’s Messaging tier first
Members see less than the team allows	A scoped module is limited by the team’s brand or location selection	Widen the Scope, or add the missing locations to the selection
Members see more than you intended	They belong to another, more permissive team	Check the Teams column on the Users tab — access is the union of all their teams