Understanding User Roles

Created by Team Momos, Modified on Fri, 9 Oct at 8:07 PM by Team Momos

TABLE OF CONTENTS


What are User Roles?

User Roles let you define what a group of team members can access and do in Momos, without setting up each user individually. A User Role combines:

  • Module permissions — which parts of the platform the role can use, and at what access level.
  • Case permissions — which cases the role can access, and whether it can view or reply to submissions.


You then assign the role to users and choose where it applies (which brands and locations). Any change to a role is applied automatically to every user who holds it.


✎ A user can hold more than one User Role. Each role's access levels apply only to the brands and locations assigned with that role. Where two roles cover the same location (or brand) and give different levels on the same module, the highest level applies there.
Example: Role A gives Manager on Reviews for Location 1, and Role B gives Viewer on Reviews for Locations 1 and 2. The user is Manager on Reviews at Location 1, and Viewer at Location 2.


Access levels

Each module in a role is set to one of the levels below. Not every module offers every level — the role editor only shows the levels that apply to that module.


LevelModule accessWorking on feedback (Reviews, Surveys, Messaging)
OwnerEverything Manager can do, plus a few extra actions on some modules (listed under each module below). On the other modules, Owner and Manager are the sameResolve, reply, comment, assign
ManagerView, create and editResolve, reply, comment, assign
ViewerView onlyComment, assign, resolve
NoneNo access — the module is hiddenNo access — feedback is hidden


ⓘ Which level should I choose? Choose Manager for day-to-day work. Use Owner only when someone needs one of the extra actions listed under a module below — for example, building surveys, creating case templates, claiming Momos Phone Numbers, or exporting customers.


Module types and where they apply

Modules are grouped by how their access is scoped.

Module typeWhat it coversWhere it applies
Global-scopedPlatform-wide featuresThe whole account — no brand or location selection needed
Brand-scopedConfiguration managed per brandThe brands you select when assigning the role
Location-scopedFeedback, customer and marketing modulesThe locations you select when assigning the role


Location options

When you assign a role, location-scoped modules can apply to:

OptionApplies to
All locationsEvery location in the account, including locations added later
All locations in specific brandsEvery location under the brands you pick
All locations in specific groupsEvery location in the location groups you pick
Specific locationsOnly the locations you pick
NoneNo locations


Include blank location: some data isn't linked to a location. Tick Include blank location to let the user see it, either for all brands or only for specific brands.


Modules

Global-scoped modules

ModuleLevels availableNotes
Manage ConnectionsManager, NoneManage the account's platform connections
Custom Integration UploadManager, NoneUpload custom integration data
Care AnalyticsViewer, NoneView Care Analytics


Brand-scoped modules

All brand-scoped modules offer Owner, Manager, Viewer and None.

ModuleNotes
Alfie ConfigAlfie's configuration for the brand
Business Info > Location GroupsThe brand's location groups
Manage CategoriesThe brand's feedback categories
Case BuilderOwner: create new case templates and edit every existing template.
Manager: edit templates within the role's Case editor scope — all templates of the assigned brands, or only the templates you pick.
Viewer: see all case templates for the assigned brands, view their QR codes, and open the public link — useful for copying and sharing the link or QR code.


Location-scoped modules

All location-scoped modules offer Owner, Manager, Viewer and None.


✎Inbox and Analytics go together.For feedback modules (Reviews, Surveys, Chat, Direct Messaging) and Offers, the same permission controls both the Inbox and Analytics. If a user can see it in the Inbox, they can see its data in Analytics for the same locations, and vice versa.


ModuleNotes
Business Info > Locations OverviewLocation details.
Owner can also claim and delete Momos Phone Numbers — the SMS numbers a brand uses to text customers through Outbound Campaigns. Manager and Viewer can see the numbers but not change them.
Customer DataControls access to the Customers module (customer profiles, audiences, traits, and data imports). It also controls whether customer personal information (name, email, phone) is visible elsewhere: in Inbox tickets, in CSV exports, and in emails sent out from Momos. Users with None see this information masked in the Inbox and in emails, and removed from CSV exports. Viewer and above can see it.
Opening the Customers module itself requires Manager — Viewer can see customer information in the Inbox, but can't open the Customers module.
Manager: open Customers, and create and edit audiences and traits.
Owner: also import trait CSVs, manage data sources (data imports) and export customers.
Direct MessagingDirect messages (e.g. Facebook and Instagram) — tickets in the Inbox and data in Analytics.
ChatChat conversations — tickets in the Inbox and data in Analytics.
OffersCovers Offer Builder, issuing offers from the Inbox, and offer data in Analytics.
Viewer: see the offers list and analytics, and issue existing offers to customers from the Inbox. Cannot create or edit offers.
Manager: also create, edit and publish offers.
Owner: also deactivate an offer that is already live.
Loyalty ActionLoyalty actions for loyalty members in the Inbox, at the ticket's location.
Viewer: see the loyalty badge, the customer's points balance and transaction history.
Manager: also send points and rewards. Depending on the loyalty platform, also deduct points or reverse a reward. Each action is logged as a comment in the thread.
Owner: same as Manager.
ReviewsReviews from all connected platforms — tickets in the Inbox and data in Analytics.
SurveysSurvey responses — tickets in the Inbox and data in Analytics.
Owner also gets the Create Survey button on the survey analytics screens (other levels see a See Surveys link instead).
Manager can delete survey tickets in the Inbox. On some accounts, this is restricted to Owner.
Survey BuilderOwner: create, edit, duplicate, and activate or deactivate surveys.
Manager: view the list of surveys, and view each survey's QR code and link — useful for sharing. Cannot create or edit.
Viewer: cannot use Survey Builder.
Surveys are deactivated rather than deleted. Survey Builder is separate from Surveys, which controls survey responses in the Inbox and Analytics.
AdsAds.
Owner can also edit connected Facebook ad accounts.
Asset LibraryAssets and templates. Manager can create and edit assets and regular email templates.
Owner can also bulk delete (Delete All on selected images and text assets), and set special email templates as default or activate them.
Outbound CampaignOutbound campaigns. Manager can create and send campaigns.
Owner can also manage email domain authentication settings.
Social MediaSocial media posts


Admin-only features

Some features are available to Account Admins only and can't be granted through a User Role, including Automation, SLA and Inbox Properties. Account Admins also have full access to every module and manage users and User Roles.


Case permissions

Case permissions control which case submissions a role can see and respond to. They are separate from the Case Builder module, which controls who can create and edit case templates.


Choosing case access for a role

In Settings > Manage Users > User Roles, edit a role and go to Case permissions. Choose:

OptionApplies to
All casesEvery case in the assigned brands, including cases created later
Selected casesOnly the cases you assign to the role
NoneNo case access


For each case, set what the role can do per inquiry type:

  • View — see submissions.
  • Reply — respond to submissions.

Select All inquiry types to include every inquiry type in the case, including ones added later.

Setting case access from a case template

You can also manage access from Care > Case Templates. Open a template's Permissions:

  • Case builder tab — which roles can edit this template.
  • Inbox tickets tab — which roles can view or reply to this template's submissions, per inquiry type. Use + User role to add a role.


✎ Users only see tickets from the locations assigned to them, even if their role has access to the case.


⚠ The Cases Permissions tab in Manage Users is deprecated. Case access is now managed through User Roles.


Assigning a role to a user

  1. Go to Settings > Manage Users and open a user.
  2. Add a User Role.
  3. Under Applies To, choose the brands for brand-scoped modules and the locations for location-scoped modules.
  4. Optionally tick Include blank location.
  5. Review the case access the role grants, then click Save.


FAQ

Why can't I find Automation, SLA or Inbox Properties in the role editor?

These features are available to Account Admins only.


Why can a Viewer on Offers issue offers?

Offers covers both Offer Builder and issuing offers from the Inbox. Viewer lets frontline staff issue existing offers without being able to change them.


What's the difference between Owner and Manager?

On many modules there is no difference. Owner adds extra actions on: Business Info (Momos Phone Numbers), Customer Data (data imports and customer export), Offers (deactivate live offers), Surveys (create-survey shortcut, and survey ticket delete where restricted), Survey Builder (create and edit surveys), Ads (Facebook ad accounts), Asset Library (bulk delete, special email templates), Outbound Campaign (domain authentication) and Case Builder (create new templates).


Can non-Admins invite other users?

No. Only Account Admins can manage users and User Roles.


Managing User Roles

Creating user roles and inviting users

Editing a user role


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article