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
  • Understanding User Roles and Permissions
  • Basics of Roles and Permissions

Was this helpful?

  1. SERVICES
  2. Brand Settings (Branding)

What are Permissions and Roles?

Last updated 2 months ago

Was this helpful?

Role-based access control (RBAC) describes the process of assigning permissions to roles and then assigning roles to users. This approach simplifies user access management and ensures that users have the appropriate permissions to perform their job functions. We can call it RBAC or Roles & Permissions to simplify the name.

To learn more about this concept of database & coding reflection, please visit Glossary () or .

Understanding User Roles and Permissions

In modern applications, managing the access and capabilities of users is crucial. This is often achieved through the implementation of roles and permissions. Understanding the distinction and application of these two elements is key to creating secure and efficient users.

Basics of Roles and Permissions

  • are specific actions or access levels granted to users or roles. Permissions define what a user can or cannot do within an application. For instance, permission might allow a user to view a document but not edit it. Permissions are granular and focused on specific actions or resources.

  • : Roles are collections of permissions designed to represent a set of responsibilities or a job function. By grouping permissions into roles, you can more easily manage what users can do based on their job duties or organizational status. Roles simplify the assignment of permissions and ensure consistency across similar user types.

glossary.jframework.io
TechDictionary.org
Permissions
Roles
Relationship between permissions and roles.
Drawing