Cryptlex Documentation
  • Welcome to Cryptlex!
  • Getting Started
    • Overview
    • Licensing Models
  • License Management
    • License Templates
    • Implementing License Models
    • Creating Licenses
    • License Subscriptions
    • Custom License Fields
    • Meter Attributes
    • Suspending Licenses
    • Revoking Licenses
    • Maintenance Policies
  • Feature Management
    • Overview
    • Features and Entitlement Sets
    • License Feature Entitlements
    • Accessing Feature Entitlements
    • Use Cases
  • User Management
    • Roles
    • Creating Users
    • Authenticating Users
    • Organizations
    • Resellers
    • Customer Portal
    • Reseller Portal
    • Google SSO
    • SAML SSO
  • Release Management
    • Overview
    • Creating Releases
    • Distributing Releases
  • Node Locked Licenses
    • Overview
    • Using LexActivator
      • Using LexActivator with C, C++ and Objective C
      • Using LexActivator with C#
      • Using LexActivator with VB.NET
      • Using LexActivator with Java
      • Using LexActivator with Delphi
      • Using LexActivator with Python
      • Using LexActivator with Go
      • Using LexActivator with Node.js
      • Using LexActivator with Ruby
      • Using LexActivator with Android
      • Using LexActivator with iOS
      • Using LexActivator with Flutter
    • Using Web API
    • Offline Activations
    • Proxies and Firewall
  • Floating Licenses
    • Overview
    • Hosted Floating License Server
    • On-Premise Floating Licenses
      • LexFloatServer
      • Using LexFloatClient
        • Using LexFloatClient with C, C++ & Objective C
        • Using LexFloatClient with C#
        • Using LexFloatClient with VB.NET
        • Using LexFloatClient with Java
        • Using LexFloatClient with Delphi
        • Using LexFloatClient with Python
        • Using LexFloatClient with Node.js
        • Using LexFloatClient with Go
        • Using LexFloatClient with Android
        • Using LexFloatClient with iOS
      • Offline Floating License
  • Named User Licenses
  • Timed Trials
    • Verified Trials
    • Unverified Trials
  • Licensing Docker Apps
  • Webhooks
  • Automated Emails
  • Web Integration
    • Personal Access Tokens
    • Using Web API
    • Using Zapier
    • Using FastSpring
    • Custom Development
  • Changelog
    • Web API
    • LexActivator
    • LexFloatClient
    • LexFloatServer
  • Legal
    • Terms of Service
    • Privacy Policy
    • Subprocessors
    • Data Processing Addendum
    • Service Level Agreement
    • Security, Privacy, and Compliance
    • Open Source Licenses
  • Cryptlex On-Premise
    • Overview
    • System Requirements
    • Server Layout
    • Installation Guide
      • Docker Compose
      • Kubernetes
    • Configuring Client Libraries
    • Monitoring and Error Reporting
Powered by GitBook
On this page
  • Super Admin role
  • Admin role
  • Custom roles
  • User role
  • Organization admin role
  • Reseller admin role
  1. User Management

Roles

Roles help you manage authorization, which enables you to specify the resources that users in your application are allowed to access.

Each account has five reserved roles: super-admin, admin, organization-admin, reseller-admin and user.

Super Admin role

Has full access to all functions of the account. There can be only one super-admin per account. This role is assigned to the user who registers for the Cryptlex account.

Admin role

Admin role gives your team members complete control of the account except for account deletion, deleting another team member with an admin role and changing roles of team members.

Any team member with an admin role is counted against the admins in your plan.

Custom roles

You can also create custom roles with fine-grained permissions and assign them to your team members.

Any team member with a custom role is counted against the admins in your plan.

User role

The user role is meant for your customers to whom you want to license your product. This role permits the users to view their licenses, activations and releases (if any) for the product for which they have licenses.

Any user with a user role is counted against the users in your plan.

Organization admin role

Customers can either be individual users or entire organizations. For organizations requiring the autonomy to set up user profiles, form user groups, and allocate licenses, assign the 'organization-admin' role. This empowers them to oversee their license distribution and usage internally.

Any user with an organization-admin role is counted against the users in your plan.

Reseller admin role

The "reseller-admin" role grants users the ability to view and manage all licenses associated with customers under their reseller account. Additionally, they can create and manage users and organizations, as well as assign licenses as needed. This role enables resellers to efficiently manage licensing and customer access within their reseller account.

PreviousUser ManagementNextCreating Users

Last updated 2 months ago