What is Permission Management?

Permission Management in GTG CRM helps businesses clearly define: - What each user can view - Which data they can edit - Which actions they are allowed to perform within the system

By setting up roles (roles) with specific permissions, businesses ensure that each person only performs their assigned tasks.

Why Do Businesses Need Permission Management?

Risks of NOT Having Permission Management

Problem Consequence
Data accessed freely Customer information, revenue compromised
Overlapping tasks Multiple people working on the same task
Uncontrolled errors Accidental deletion or modification of critical data
Sensitive information leaked Employees see salaries, expenses, strategies

Benefits of Having Permission Management

Benefit Description
Secure Operations Each person only sees/does their assigned part
Prevent Errors No one accidentally deletes/modifies critical data
Easy Scalability Adding new employees just requires assigning a role
Easy Management Clear understanding of who does what, clear responsibilities

Default Roles

GTG CRM provides 3 default roles:

Administrator

  • Highest privilege in the system
  • Can perform all actions on the platform
  • Automatically has access to Settings

Marketing Manager

  • Manages marketing campaigns
  • Views reports, statistics
  • Manages the marketing team

Marketing Staff

  • Performs daily marketing tasks
  • More limited permissions than Manager

Custom Permissions by Module

Customize permissions for each module with toggle on/off:

Module Permissions that can be granted
Automation Workflow Create, View, Update, Delete
Landing Page Create, Update, Publish, Unpublish, Delete, Modify Custom Domain
Marketing View Social Posts, Manage Campaigns
CRM View All Contacts, Import, Export, Edit, Delete
Email Create, Send, View Reports
Messaging View, Reply, Manage Channels
Product Hub Manage Products, View Inventory
E-commerce Manage Orders, View Reports
Billing View Invoice, Manage Payment
Settings Manage Workspace, Manage Users

Standardized Permission Names: DOMAIN_ACTION_OBJECT

Naming Convention

All permission names in GTG CRM are standardized according to Convention A - DOMAIN_ACTION_OBJECT:

DOMAIN_ACTION_OBJECT
  │         │       │
  │         │       └── Object (what is being acted upon: INVOICE, USER, CONTACT...)
  │         └── Action (the action: VIEW, CREATE, MANAGE, DELETE...)
  └── Domain (the area: BILLING, WORKSPACE, CRM, AUTOMATION...)

Examples of Convention A Permission Names

Domain Permission Name Meaning
BILLING_ BILLING_VIEW_INVOICE View invoice
BILLING_ BILLING_ADD_PAYMENT_METHOD Add payment method
WORKSPACE_ WORKSPACE_ACTION_USER Manage workspace users
WORKSPACE_ WORKSPACE_VIEW_BILLING_MEMBER View billing information
AUTOMATION_ AUTOMATION_WORKFLOW_CREATE Create automation workflow
AUTOMATION_ AUTOMATION_WORKFLOW_DELETE Delete automation workflow
CRM_ CRM_OBJECT_VIEW View CRM object
CRM_ CRM_VIEW_ALL_CONTACT View all contacts

Why is Convention A Necessary?

Previously, permission names were inconsistent: SEND_EMAIL, CREATE_LANDING_PAGE, VIEW_BILLING — making them difficult to understand and manage as businesses accumulated dozens of different permissions.

Convention A solves this problem by: - Clear grouping by Domain → easy to find related permissions - Consistent actions → VIEW always means view, CREATE always means create - Easy auditing → just search for BILLING_ to see all billing-related permissions

Administrator Automatically Accesses Settings

Users with the Administrator role automatically have access to all Settings — no additional permissions need to be assigned.

Permission Management Process

┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│ Create Role │ ─► │  Custom     │ ─► │ Assign Role │
│   new       │    │  Permissions│    │   to User   │
└─────────────┘    └─────────────┘    └─────────────┘
      │                  │                  │
      ▼                  ▼                  ▼
   Name,             Toggle each          Select user,
   description       permission         select role

Example: Permission Management for Departments

Role Main Domain Example Convention A Permissions
CEO/Owner All Administrator
Sales CRM, Messaging, Email CRM_VIEW_ALL_CONTACT, CRM_OBJECT_VIEW
Marketing Marketing, Ads, Landing Page AUTOMATION_WORKFLOW_CREATE, LANDING_PAGE_CREATE
Support Messaging, Ticket CRM_OBJECT_VIEW (read-only)
Warehouse Product, Order (module-specific)
Finance Billing BILLING_VIEW_INVOICE, BILLING_ADD_PAYMENT_METHOD

Conclusion

With Permission Management in GTG CRM:

  • Expand your team while maintaining control
  • Protect your business's critical data
  • Standardized Convention A permission names - clear, easy to audit
  • Administrator automatically has Settings - no more misconfigurations
  • Operate professionally like a large enterprise