📘
Sinch | Documentation Global
  • Introduction
  • Glossary
  • GETTING STARTED - MENU
    • Sinch Messaging Platform
      • Login, Language & Menu
      • Account & Settings
      • Dashboard
      • Contacts
      • Groups
  • Credits and limits
    • Signing of plans
    • Limits
  • Send a message
    • Send a fast message
    • How to Send a Message
    • How to Set Up a File
    • Mapped errors
    • Campaigns
    • Correlation ID
    • Tracking Sent Messages
    • Cancelling a Message
    • Character Limit Setting
    • MM2: New Report: Chat (MT + MO)
    • SMS Report > RCS
  • Reports
    • Viewing & Exporting Reports
      • New WhatsApp Conversation report
      • Getting to know the new reports
    • Saved Reports
    • WhatsApp Lists
    • Billing Report
  • Permission
    • System User Role
    • Managing Customers | Subaccounts
    • Permission Levels
    • Subaccounts & Users
    • IP Restriction
    • Two-step Verification
  • SMS
    • SMS Template
    • SMS BOT
  • RCS
    • RCS (Native)
  • WHATSAPP
    • WhatsApp Embedded Signup
      • Prerequisites
      • Registering your WhatsApp Number
      • Verifying your Company on Business Manager
      • Potential Errors During the Embedded Signup Flow
    • Human Assistance Policy
    • WhatsApp Guidelines
    • Instructions & Good Practices
      • Channel Rules
      • Learn More About Tiers
      • Good Practices
    • WA Template - What Is It?
    • Registering a Template
    • Deleting a WA Template
    • WhatsApp Account Settings
    • WhatsApp Dashboard
    • Tech Providers - What is it and how does it work?
  • IA CONVERSATIONAL
    • Planning your bot
    • Creating a new bot
    • Adding content to your bot
      • Detecting information in expressions
      • Asking user info through input validation
      • Flow navigation with variables
    • Bot dialogs
      • Bot message
      • Go To
      • Input Validation
      • Action
    • Publishing & platform URLs FAQ
  • TECHNICAL DOCUMENTATION
    • API & Integrations
      • Introduction - Integrations
      • SMS API
      • Email API
      • Fallback API
      • WhatsApp API
      • WhatsApp Groups API
      • Listing Message Templates
      • WhatsApp Interactive API
      • WhatsApp Lists via API
      • WhatsApp Messaging via SFTP
      • Campaigns API
      • TTL - Time to Live
      • Webhook
  • SUPPORT
    • Status
    • Glossary - Status Page Components
    • Support
  • STATUS PAGE
    • Components status page
      • Integrations
        • SMPP
        • Web service API
        • Web Interface
      • Callback / Delivery Report
        • Webhook DLR (delivery to handset)
        • SMPP DLR (delivery to handset)
        • SMPP Callback (delivery to carrier)
        • Webhook Callback (delivery to carrier)
      • OPERATORS
      • WhatsApp Sending messages to the user (MT)
        • Internal Queues MT
      • WhatsApp Receiving User Messages (MO)
        • Internal Queues (MO)
Powered by GitBook
On this page
  • What is this new feature?
  • Activating the System User Role
  • Deactivating the System User Role
  • Generate a new token
  • Webhook Configuration: prepare to Chatlayer integration
  • Update Chatlayer with System User

Was this helpful?

  1. Permission

System User Role

PreviousBilling ReportNextManaging Customers | Subaccounts

Last updated 2 years ago

Was this helpful?

What is this new feature?

Before we explain about the feature, we need to understand the problem that we are solving. When you have to create a chatbot integrated to MM2, you must create an account on MM2 to link this to a chatbot, on Chatlayer. If this person who has created this bot leaves the company, this chatbot usually is desactivate due to this event.

So, thinking in avoid this bad experience happen always that someone leaves the company (and to guarantee more security in our process), we have decided to create the System User Role. This new feature intend to prevent this issue from happening, become able to create safe users to use on your chatbots.

Activating the System User Role

Go to Settings > My Account > Account Settings

2.1 - You can see the new tab called System User.

Only the customer Admin and the Developer role can be able to set up this new configuration.

2.2 - Button to "Create System User".

2.3 - Once you click on the button to create a new system user, it will open a pop up where you can select the subaccount + username.

2.4 - It is important to know that you can only create a system user for each subaccount.

The Username can be whatever you want.

2.5 - After you define the subaccount and the username, you will click on Generate Token.

It will appear this pop up, so pay attention to take note of this token because it will not be displayed again. In case you forget to take a note, you will have to generate a new token.

In this screen, you can see all the system users you have created.

2.6 - You can see who user has created.

2.7 - All the informations that belongs to the system user.

2.8 - You will be able to see just the end of the token.

2.9 - The date and the time of this creation.

2.9.1 - If it is active or inactive.

2.9.2 - More Actions (Deactive or Generate a new Token)

Deactivating the System User Role

Go to Actions > Click on … > Deactivate.

3.1 Once you click on Actions and choose to deactivate the System User, it will open a pop up to confirm your choice.

3.2 After doing this, you will see the Status column updated. In case you want to activate it again, just go to Actions.

Generate a new token

Go to Actions > Click on … > Generate a new token.

4.1 - Once you click on Actions and choose to Generate a new token, it will open a pop up to ensure your understanding about the risk of doing this (just in case you have configured in an API).

Webhook Configuration: prepare to Chatlayer integration

Go to Settings > Webhook.

5.1 This configuration is the same of usual.

The only exception is that if your chatbot is not so active into sending messages and not expecting to receive organic MO (mainly after so much time without any interaction), you will have to configure another Answer (MO) to accept Subaccount Null.

Update Chatlayer with System User

Go to Chatlayer > Configure Wavy WhatsApp Channel

6.1 This configuration is the same of usual.