Appflow.ai
Visit our websitePricingSign up for freeLog in
  • GET STARTED
    • What is Appflow.ai?
    • Quickstart - How to start working with Appflow.ai?
    • FAQ
    • Ownership and other roles
  • SDK Set-up Instructions
    • Android SDK
      • Google Play Store Credentials
        • Google Service Account Key
        • Google real-time developer notifications(RTDN)
        • FCM server key(optional)(to be updated)
      • Events (Custom events)
      • Purchases
      • Visual constructor
      • User info
      • Push notifications
    • iOS SDK
      • Specify Apple Store Keys
      • Purchases and User Info
      • Event tracking (Custom events)
      • Push Notifications Configuration
      • Visual constructor
  • IN-APP PURCHASE
    • SKU adding
  • METRICS & EVENTS
    • Calculations of Analytics
    • Terms and Descriptions
    • Purchase Events
    • In-app Events
    • Events Structure
    • End-users Attributes
    • Users' statuses
  • SUBSCRIPTION ANALYTICS
    • Dashboard
    • Configurator
    • Reports
    • A/B Testing
    • Integrations
    • Create Push-notifications
    • In-app Messages
    • Return of Advertisement
    • Funnels
    • Funnel 2.0 BETA
    • Entitlements
    • Visual Constructor
  • INTEGRATIONS
    • Adjust
    • Appsflyer
    • Mixpanel
    • Webhooks
    • Apple Search Ads Attributions
    • Branch
    • Amplitude
  • OTHERS
    • Pricing plans and important information about your payments
    • Storing your data
    • Privacy Policy
    • Terms of Use
    • Unsubscribe from Appflow.ai
Powered by GitBook
On this page

Was this helpful?

  1. GET STARTED

Ownership and other roles

Description about roles and how to add new members

PreviousFAQNextAndroid SDK

Last updated 1 year ago

Was this helpful?


Preamble

The purpose of this document is to define the ownership and other roles that can be set within the admin panel of our software. By using our role-based access control feature, organizations can ensure that team members have access only to the features and data that are relevant to their roles and responsibilities.

We believe that role-based access control is an essential feature for organizations that want to maintain a high level of security and control over their data. This document outlines the responsibilities and permissions of each role and provides guidance on how to set up and manage roles within our software.

By following the guidelines in this document, organizations can create a secure and efficient team environment that maximizes the productivity of their analyses.

In Appflow.ai we have 3 types of roles: owner, moderator. reader.

  • Owner: You can see, edit or delete members of your project.

  • Moderator: Same right as owner such as A/B tests creation. Push-notification campaigns management, visual constructor details editing. The moderator doesn't have the right to change members and add apps to your project.

  • Reader: View-access only, but can play with filters to see the data for the needed period.

Right now we are using emails as members ids so you can invite a new member through the email by choosing the name, role, and email. If the user accepts your invite, he will be added to the project. Please, note, there is a member limitation for different .

plans