What is Permissions?

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

By setting up roles with specific privileges, businesses ensure that each person performs only their designated tasks.

Why Does Your Business Need Permissions?

Risks of NOT Having Permissions

Problem Consequence
Free access to data Customer information and revenue are leaked
Overlapping work Multiple people working on the same task
Uncontrolled errors Accidental deletion or modification of important data
Confidential information leakage Employees see salaries, expenses, and strategies

Benefits of Having Permissions

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

Default Roles

GTG CRM provides 3 default roles:

Administrator

  • The highest authority in the system
  • Can perform all actions on the platform
  • Automatically has access to Settings

Marketing Manager

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

Marketing Staff

  • Performs daily marketing tasks
  • Has more limited permissions than a Manager

Custom Permissions per Module

Customize permissions for each module with toggle switches:

Module Permissions Available
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 Naming: DOMAIN_ACTION_OBJECT

Naming Convention

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

DOMAIN_ACTION_OBJECT
  │         │       │
  │         │       └── Object (the entity 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 objects
CRM_ CRM_VIEW_ALL_CONTACT View all contacts

Why is Convention A Needed?

Previously, permission names were inconsistent: SEND_EMAIL, CREATE_LANDING_PAGE, VIEW_BILLING — making them difficult to understand and manage as a business grows and accumulates 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 related billing permissions

Administrators Automatically Access Settings

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

Permission Process

┌─────────────┐    ┌─────────────┐    ┌─────────────┐
│  Create New │ ─► │  Custom     │ ─► │  Assign Role│
│  Role       │    │  Permissions│    │  to User    │
└─────────────┘    └─────────────┘    └─────────────┘
      │                  │                  │
      ▼                  ▼                  ▼
   Set name,          Enable/disable     Select user,
   description       individual         select role
                      permissions

Example: Assigning Permissions to Departments

Role Primary 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

Summary

With Permissions in GTG CRM:

  • Scale your team while maintaining control
  • Protect your critical business data
  • Standardized Convention A permission names – clear and auditable
  • Administrators automatically get Settings access – no more misconfigurations
  • Operate professionally like a large enterprise