Flochat
API DocumentsWebsiteLog in
  • Start Here
    • Welcome 👋
    • Getting Support
    • FAQ's
    • Pricing Plans
  • GETTING STARTED GUIDE
    • Introduction
    • Set your goals
    • Building your chatbot
    • Maintain success
  • CHATBOT GUIDE FOR BEGINNERS
    • Introduction
    • What is a chatbot
    • Channels
    • Benefits & importance
    • Use cases
  • PLATFORM
    • Introduction
      • Change Password
      • Forgot Password
      • Getting Started Checklist
      • Platform Overview
      • Workspaces & Members
      • Integrations
        • Stripe
        • PayPal
        • Cloudinary
        • Shopify
        • Facebook Business
        • Calendly
        • Slack
        • Google Sheets
        • Data Store
        • Twilio
        • Signalwire
        • Email (SMTP / Gmail)
        • MailChimp
        • VideoSdk
      • Ecommerce
        • Setup Ecommerce
        • Use Ecommerce in the Flow
    • Connect to Channels
    • Website Chat
    • WhatsApp + 360Dialog
    • Email Templates
    • WhatsApp Cloud
  • Flow Builder
    • Flow builder overview
    • Field variable
    • Steps
      • Steps
      • Question step
      • Variable Operation
      • JSON Operation
      • External Request
      • Send Notification
      • Condition Step
      • Split Step
      • Go To Step
    • Sub Flows
      • Sub Flow
      • Workflow
      • Function Flow
  • Artificial Intelligence
    • OpenAI | ChatGPT
      • Connect OpenAI
      • Chat with AI Basics
      • What are Functions
        • Functions in Flows
        • Capturing Data
        • Generate function with AI
        • Combine chat completions & Functions
      • What are Embeddings
        • Create Embeddings
        • Add Embeds to your Flow
        • Error Handling
        • Combine Embeddings with Functions
    • GitBook Lens AI
  • Mini Apps
    • Stealth Seminar
  • Users
    • Live Chat
    • Bot Users
  • Bot Automation
    • Keywords
    • Sequences
    • Triggers
    • Comment Keywords
  • Contents
    • Custom Fields
    • Tags
    • One Time Notification (Facebook)
    • Personas
    • Menus
    • Customer Feedback (Facebook)
  • Tools
    • Error Logs
    • Testers
    • Admins
    • Multi Languages
    • Inbound Webooks
  • Broadcasting
    • Broadcasts
  • Developers
    • Chatbot API
  • BETA LAUNCH
    • Day One
Powered by GitBook
On this page
  • Invite and manage admins
  • How to set up an admin flow
  1. Tools

Admins

PreviousTestersNextMulti Languages

Last updated 2 years ago

Besides the regular members, you can invite to your workspace you can also invite admins to your chatbot only.

With a condition you can set up admin menus for them they can access like getting a report or wanting to get some insights into the chatbot.

Invite and manage admins

To invite an admin go to Tools from the left-hand menu and select the Admins tab on top.

From here you will get to the main overview.

To add a new admin the user you want to invite needs to be a subscriber to your chatbot. If they are then press the button on the top-right corner named + New Admin.

From here a pop-up window will appear where you can search for and add a new admin.

Just type in the name of the person you want to have as an admin and press the plus sign to have them added as an admin. Once you press the plus sign you will return to the main menu where you can manage all admins.

At the right of each admin, you have the option to delete them if you like.

How to set up an admin flow

Now that you have appointed an admin you can set up admin specific flows for them. This is ideal if you want to give a business owner some insights as to what is going on inside the chatbot but don’t want to give access to the backend of that chatbot.

Just go to any flow you like and insert a condition block. From here search for the condition Is Admin.

If the condition is set to yes you can send the admin to the admin mode where you can set up access to whatever you like.

An example could be;

It is a great way for business owners to get access to certain features on the front end while not having to worry about them having access in the backend.