LogoLogo
Developers
  • Welcome
  • Introduction
  • Getting Started
    • Overview
    • What can we do?
    • Features & Packages
    • SDKs
  • SERVICES
    • Introduction about services
    • Identity
      • Brand
        • Examples
        • How to identify a brand
        • What default values when a brand is created?
        • How to be a reseller
        • Multiple Brand Management
      • User *
        • User Type
        • Username
        • User Status
        • Username vs. Login Name
        • Password
          • User-defined options
          • Built-in policies
        • Authentication Methods
          • Traditional Login
          • External Login
          • Login with Email link
        • Referral (Invite Friends)
          • Example
        • Password Policy
        • Login with Google
      • Device
        • Type
        • Device Identifier (Device Code)
        • Device Registering
        • Access Limit
    • Subscription
      • What is Package?
      • Package (Pricing Plan)
      • Plans & Pricing *
        • Licensing *
        • Subscription Type *
        • Feature
          • Examples
        • Package
        • Price *
        • Coupon
        • License
          • License Status
          • License Delivery Type
          • License Source
        • Pseudo Flow *
          • Licensing Flow *
          • Pricing Flow *
          • Coupon Application Flow *
    • Billing
      • Payment
        • Payment Status
        • Commission
        • Instant Payment Notification (IPN) *
          • Payment Gateway
          • Supported Gateways
        • Payment Transaction Overview
      • Transaction *
      • Invoice *
    • Wallet
      • Wallet *
        • Secure Practices *
        • ✔️Pseudo Flow *
      • Redeem *
    • Security
      • Black List
      • Risk Levels
    • Community
      • Issue
        • Examples
        • Pseudo Flow
      • Organization
    • Content Delivery Network (CDN)
      • CDN
        • CDN Storage
        • Uploading files to a CDN
        • Downloading files from a CDN
        • Are There Any Limitations?
        • Best Practices
    • Analytics
      • Tracking
        • Tracking Activity
        • Tracking Email
        • Tracking Notification
      • Log & Debug
      • Notification
    • Integration
      • Authentication
      • Payment Gateways
      • Push Notification
      • SMS Provider
      • SMTP Provider
      • Gitbook
    • Brand Settings (Branding)
      • What are Permissions and Roles?
        • System permissions & brand-based permissions
          • A (6 resources)
          • B (7 resources)
          • C (4 resources)
          • D (3 resources)
          • E (2 resources)
          • F (1 resource)
          • I (3 resources)
          • L (1 resource)
          • O (1 organization)
          • P (4 resources)
          • R (1 resource)
          • S (2 resources)
          • T (4 resources)
          • U (7 resources)
          • W (1 resource)
        • System Roles & Brand-based Roles
        • Granting Permissions
        • Assigning Roles
        • Best Practices
        • Pseudo Flow
        • Conclusion
      • What is Issue Category
      • What is Feature?
      • What is Subscription Type?
      • What is Subscription?
      • What is Commission Rate?
      • Events & Patterns
        • Event
          • Events for Community (Organization) (4)
          • Events for Device (3)
          • Events for License (2)
          • Events for Payment (8)
          • Events for System (9)
          • Events for Ticket (Issue) (6)
          • Events for User (47)
            • User.Account_ (5)
            • User.Coupon_ (1)
            • User.Email_ (5)
            • User.Expiration_ (3)
            • User.Inactive_ (2)
            • User.Invoice_ (1)
            • User.License_ (1)
            • User.Logged_ (3)
            • User.Password_ (3)
            • User.Phone_ (2)
            • User.Profile_ (2)
            • User.Receipt_ (1)
            • User.Referee_ (1)
            • User.Registered (2)
            • User.Reward_ (3)
            • User.Service_ (1)
            • User.SMS_ (1)
            • User.Status_ (5)
            • User.Suspicious_ (4)
            • User.Ticket_ (1)
          • Events for Wallet (4)
          • (Missing Events) *
        • WalletEarningEvent
          • Earning.User_ (8)
          • Earning.Wallet_ (2)
        • Email Templates *
        • SMS Templates *
      • Tags
      • Domains
      • Email templates
    • System Constants (Read-only)
      • Country
      • State
      • City
      • Time Zone
      • Currency
      • Language
      • Exchange Rate
  • Other concepts
    • Built-in resource
      • Built-in roles
        • Best practice
      • Built-in permissions
    • JFW Status
    • Default data
    • System data
    • Soft deletion data
    • Cryptography
    • Mailing
      • Examples
      • Email Sender
      • Email Template
    • Scheduler
      • Examples
      • Schedulers Used In JFW
    • Tracking Level
  • Versioning
  • Workflows
  • References
    • Internal references
    • External references
      • MailKit
      • MIME Type
  • Changelog
Powered by GitBook
LogoLogo

For developers

  • Developers

For users

  • Admin & cPanel

Examples

  • BoostPTE

Copyright @2018-2025

On this page
  • JFW Built-in roles
  • 1. Super Admin
  • 2. Brand Owner
  • 3. User Manager
  • 4. Support Staff
  • 5. Billing
  • 6. Marketing
  • 7. Reader
  • 8. Tester
  • 9. IT Staff
  • Summary

Was this helpful?

  1. Other concepts
  2. Built-in resource

Built-in roles

JFW Built-in roles

This document provides a comprehensive overview of the built-in roles available in the system. Each role is designed to ensure secure and efficient access management, enabling users to perform their tasks without compromising system integrity. Below is a detailed breakdown of each role, its purpose, and associated permissions.


1. Super Admin

Description:

The Super Admin is the highest-level role in the system, with unrestricted access to all features and functionalities. This role is responsible for overseeing the entire system, including all brands and global configurations.

Permissions:

  • Brand Management: Create, edit, and delete brands.

  • Global Settings: Configure system-wide settings, including database and licensing.

  • User Management: Manage users, roles, and permissions at the system level.

  • Monitoring: Access and monitor all logs and events across the system.

  • Full Access: Unrestricted access to all features and functionalities.


2. Brand Owner

Description:

The Brand Owner role is assigned to administrators of individual brands. They have full control over their brand's resources but cannot access or modify other brands.

Permissions:

  • Resource Management: Manage all resources within their brand, including users, roles, permissions, logs, events, and devices.

  • Full Administrative Access: Complete control over their brand's settings and features.


3. User Manager

Description:

The User Manager role is designed for individuals responsible for managing users within a specific brand. This role focuses on user administration and permission assignment.

Permissions:

  • User Management: Add, delete, and modify user information.

  • Role and Permission Management: Assign roles and permissions to users within the brand.


4. Support Staff

Purpose:

The Support Staff role is tailored for customer support teams within a brand. It enables them to assist users with product or service-related issues effectively.

Permissions:

  • Error Logs: Access user error logs for troubleshooting.

  • User Information: View user details without the ability to modify them.

  • Support Tickets: Create and track support tickets, issues, and help desk requests.

  • Device Management: Access the list of devices and their statuses.

  • Restrictions: Cannot edit users, roles, or system configurations.


5. Billing

Purpose:

The Billing role is designed for the finance team of a brand. It allows them to manage financial transactions, subscriptions, and reporting.

Permissions:

  • Payment Management: View payment reports, manage payments, and process refunds.

  • Invoices: Handle invoices and billing-related tasks.

  • Subscriptions: Manage subscription plans and active services.

  • Restrictions: Cannot edit roles, manage users, or configure brand settings.


6. Marketing

Purpose:

The Marketing role is intended for the marketing team of a brand. It provides tools to manage campaigns, track performance, and engage with users.

Permissions:

  • Ad Management: Create and manage advertisements.

  • User Engagement: Send emails and notifications to users.

  • Analytics: View statistics and reports related to ad performance and campaigns.

  • Restrictions: Cannot access logs, manage users, or modify system settings.


7. Reader

Description:

The Reader role is for users who require read-only access to information within a brand. This role is ideal for individuals who need to view data without making changes.

Permissions:

  • Read-Only Access: View all information within the brand, including users, roles, permissions, logs, events, and devices.

  • No Modification Rights: Cannot edit, delete, or create any data.


8. Tester

Purpose:

The Tester role is designed for quality assurance (QA) teams or individuals responsible for testing system features and functionalities.

Permissions:

  • Test Environment Access: Access testing environments and features.

  • Create Test Data: Generate and manage test data.

  • Submit Bug Reports: Report issues or bugs encountered during testing.

  • Restrictions: Cannot modify production data or access sensitive system settings.


9. IT Staff

Purpose:

The IT Staff role is for the IT department, responsible for maintaining system infrastructure and resolving technical issues.

Permissions:

  • System Maintenance: Access system logs and perform maintenance tasks.

  • Troubleshooting: Resolve technical issues and monitor system health.

  • Device Management: Manage and monitor devices connected to the system.

  • Restrictions: Cannot modify user roles, permissions, or financial data.

Summary

The built-in roles in the system are designed to streamline access management and ensure that users have the appropriate level of control over their tasks. By assigning these roles thoughtfully, organizations can maintain security, improve efficiency, and ensure compliance.

For further customization or the creation of additional roles, please refer to the system documentation or contact your system administrator.

Last updated 1 month ago

Was this helpful?